Date: Fri, 22 Oct 2004 23:26:53 -0400 From: Jim Trigg <jtrigg@spamcop.net> To: freebsd-ports@freebsd.org Subject: Re: ports/www is too full Message-ID: <20041023032653.GC8336@spamcop.net> In-Reply-To: <20041023001812.GA24347@it.ca> References: <20041022074529.GN10363@k7.mavetju> <41791AF7.2050009@vonostingroup.com> <200410221824.12294.benlutz@datacomm.ch> <20041022201425.GA36702@it.ca> <20041022165221.3c66232a@zork> <20041023001812.GA24347@it.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Oct 22, 2004 at 08:18:12PM -0400, Paul Chvostek wrote:
> On Fri, Oct 22, 2004 at 04:52:21PM -0600, Robin Schoonover wrote:
> > >
> > > A single directory with 12000 subdirectories in it may be unruly ...
> > > and we'd have to fix oddities like hydra, jags, replay, etc ... but it
> > > would provide for the most flexible expansion, and the symlink tree
> > > would provide an equivalent interface to folks comfortable with the
> > > current setup.
> >
> > Population. cvs (and probably cvsup) do not handle symlinks well. You
> > would have to have a script populate symlinked ports into the categories
> > by hand.
>
> If 12000 is just too frickin' many for a directory, perhaps some "titan"
> categories could be used to aggregate ports as they are now: app, devel,
> sysutil. Whatever would have the least chance of category overlap.
> MOVED can then still point to the new location, and cvsup may be a
> little happier.
Or All could be divided into prefix directories -- ports/a/p/apache20.
That would still break the number of ports per directory down enough,
leave no confusion as to where the core port directory is, and eliminate
the MOVED file. Then use the script to populate the symlink category
directories.
Jim
--
Jim Trigg, Lord High Everything Else O- /"\
\ / ASCII RIBBON CAMPAIGN
Hostmaster, Huie Kin family website X HELP CURE HTML MAIL
Verger, All Saints Church - Sharon Chapel / \
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041023032653.GC8336>