Home | History | Annotate | Line # | Download | only in sets
README revision 1.2
      1 #	$NetBSD: README,v 1.2 1998/01/09 18:56:50 perry Exp $
      2 
      3 From cgd (a] alpha.bostic.com Mon Jul 18 02:06:15 1994
      4 Received: from alpha.bostic.com (alpha.BOSTIC.COM [198.3.132.5]) by sun-lamp.cs.berkeley.edu (8.6.9/8.6.9) with SMTP id CAA18402 for <port-masters (a] sun-lamp.CS.Berkeley.EDU>; Mon, 18 Jul 1994 02:01:32 -0700
      5 Received: by alpha.bostic.com; id AA06610; Mon, 18 Jul 1994 05:02:11 -0400
      6 Message-Id: <9407180902.AA06610 (a] alpha.bostic.com>
      7 To: port-masters (a] sun-lamp.CS.Berkeley.EDU
      8 Cc: cgd (a] alpha.bostic.com
      9 Precedence: special-delivery
     10 X-Notice: Do not redistribute in any form without prior explicit
     11           consent of the author.
     12 Subject: distribution sets, etc...
     13 Date: Mon, 18 Jul 1994 05:02:11 -0400
     14 From: "Chris G. Demetriou" <cgd (a] alpha.bostic.com>
     15 Status: R
     16 
     17 [ this is also going in a README in the 'sets' directory... ]
     18 
     19 well, i've finally sat down and started doing distribution set
     20 stuff in a "nice, machine-independent way."  Should have done
     21 it months ago, but too much other stuff going on then...
     22 
     23 anyway, grab ~cgd/sets.tar.gz -- it's three scripts, and a bunch
     24 of files.
     25 
     26 the scripts should be run from the directory where they reside.
     27 
     28 makeflist:	output the list of files that should be in a
     29 		distribution, according to the contents of the
     30 		'lists' directory.
     31 
     32 checkflist:	check the file list (as internally generated
     33 		by makeflist) against the tree living in $DESTDIR.
     34 		(that tree should be made with 'make distribution'.)
     35 
     36 maketars:	make tarballs of the various sets in the distribution,
     37 		based on the contents of the lists, the tree in
     38 		$DESTDIR, and put the tarballs in $RELEASEDIR.
     39 		Note that this script _doesn't_ create the 'secr'
     40 		distribution, because (for now) it requires
     41 		manual intervention to get the binaries right...
     42 		(i'll add another script to create that dist, later.)
     43 
     44 what's in 'lists':
     45 
     46 lists describing file sets.  There are two sets of lists per file
     47 set: machine dependent and machine-independent files. (there's
     48 also another file in the 'man' dir, which is used by the 'man'
     49 and 'misc' sets, but that's explained later.)
     50 
     51 There is one machine-independent file, named "mi".  There are
     52 N machine-dependent files (one per architecture), named "md.${ARCH}".
     53 
     54 the sets are as follows:
     55 
     56 	secr:	security software -- the non-exportable bits, i.e.
     57 		those that actually use crypt, and have it compiled
     58 		in.
     59 
     60 	base:	the base binary set.  excludes everything described
     61 		below.
     62 
     63 	comp:	compiler tools.  All of the tools relating to C, C++,
     64 		and FORTRAN (yes, there are two!) that are in the
     65 		tree.  This includes includes, the linker, tool chain,
     66 		and the .a versions of the libraries.  (obviously,
     67 		base includes ldd, ld.so, and the shared versions.
     68 		base also includes 'cpp', because that's used by X11.)
     69 		includes the man pages for all the binaries contained
     70 		within.  Also, includes all library and system call
     71 		manual pages.
     72 
     73 	etc:	/etc, and associated files (/var/cron/tabs, /root,
     74 		etc.).  things that shouldn't be blindly reinstalled
     75 		on an upgrade.
     76 
     77 	games:	the games and their man pages.
     78 
     79 	man:	all of the man pages for the system, except those
     80 		listed elsewhere (e.g. in comp, games, misc, text).
     81 		Includes machine-dependent man pages for this CPU.
     82 
     83 	misc:	share/dict, share/doc, and the machine-dependent
     84 		man pages for other cpu's which happen to always
     85 		be installed.
     86 
     87 	text:	text processing tools.  groff and all of its friends.
     88 		includes man pages for all bins contained within.
     89 
     90 
     91 as noted, in addition to the "standard" files in each dir, there's
     92 a file called 'md_share' in lists/man.  it's the list of man pages
     93 that are installed from /usr/src/share, which are machine-dependent.
     94 (note that ones that are installed from elsewhere, and thus are
     95 installed on only one architecture, are listed in the md.${ARCH}
     96 file.)  basically, it's grepped through, to see which of the
     97 machine-dependent man pages that are always installed should go
     98 in the 'man' set, and which should go into the 'misc' set.
     99 
    100 
    101 I've made attempts to get the md files for the amiga, i386, hp300,
    102 pc532, and sparc done.  I've not attempted the rest (though there
    103 are empty files for all architectures except the da30, in the
    104 various directories).  I think i got the amiga, i386, and sparc
    105 done correctly, but i know that (because of weirdnesses in how
    106 their last snapshots were built) i didn't get hp300 or pc532
    107 done right.
    108 
    109 what you folks need to do:
    110 
    111 run 'checkflist' on a tree that you've created with 'make
    112 distribution'.  send me the output, and i'll take care of putting
    113 stuff on the right lists for you.  In the future, you'll get
    114 to do it yourselves, as you add programs and include files, but
    115 i'd prefer to do it the first time (unless you really want to do it
    116 yourself -- in that case, please ask me to check your suggestions
    117 re: the appropriate sets for things...)  There should be a minimal
    118 list output by checkflist -- it should all be things that
    119 _should_ be on your lsits, but aren't, i.e. machine-dependent
    120 binaries, man pages, and include files.
    121 
    122 Also, please look through the lists, and tell me if you think
    123 i've put anything in the wrong place.  i think i've
    124 taken care of all of the machine-dependence bugaboos, by
    125 doing it for the N architectures, but i'm not _sure_...  8-)
    126 
    127 
    128 thanks,
    129 
    130 chris
    131 
    132