:Sounds good, but again how will the CVSup file for ports and CVSup itself
:deal with this. Either a "refuse" file would need to be created and then
:populated or there would need to be other changes. Not sure Mr Wraith or
:the CVS maintainers would like to break down all the ports and have a
:*huge* CVSup file for ports. Or some other method would be needed that
:would increase the complexity of how the ports source is handled.
You don't. The CVS tree for ports stays the way it is, and you wouldn't
use cvsup to download a broken out version.
Here's what I would do:
* create /usr/src/ports
* create /usr/src/ports/Makefile
* make targets would be:
make install
Install a new /usr/ports. Deletes anything
previously in /usr/ports (?) and constructs a new
first-level directory hierarchy, first-level
Makefiles, /usr/ports/Mk, and aggregate DESCR file.
make update
Updates /usr/ports. Locates any broken-out
subdirectories in /usr/ports and updates them
(equivalent to cvs update in those subdirectories),
updates the Makefile's in the first-level directories,
updates the aggregate DESCR file, and updates
/usr/ports/Mk.
That's it. Most normal users can install/update their ports collection
the same way they install/update a kernel or bin or sbin, by CD'ing
into a (minimally populated) /usr/src/ports directory and typing
'make install'.
/usr/src/ports would contain nothing more then a Makefile which
cvs checkout's or cvsup's just the top level directory structure.
That handles everything except the aggregate DESCR file. I can
think of a number of trivial ways to handle the aggregate DESCR file.
Those people who are actively working with the ports hierarchy can
cvsup the whole blessed thing as they currently do.
The ports maintainers would not have to lift a finger. The ports
structure is not changing at all except for adding the ability to
create and populate a subdirectory on the fly, something that ought
to be easy to incorporate into /usr/ports/Mk, and adding /usr/src/ports
as a launching pad for standard users to install /usr/ports.
-Matt
Matthew Dillon
<[EMAIL PROTECTED]>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
