Luigi Rizzo <[email protected]> writes:

> in fact i think the biggest problem, performancewise, is the presence
> of multiple subdirs per port.

Well, if we are going to change the ports mechanism, may I suggest
that we make it easy to create `foreign' packages?  Let me explain.
In an ideal world, I'd like to use

cd /usr/ports/...
make
make package

on any of the platforms that has a ported ports mechanism (i.e. BSD
make and /usr/share/mk) in place.  Thus, I could see living with a
file directory structure as below:

+
| Makefile
| md5
|
+- FreeBSD 
|  | PLIST
|  | patches-*
|  | DESCR etc.
|     
+- SunOS
   | pkg-related files
   | patches-*

etc. 

Now this doesn't reduce the overall file/directory count, but it does
reduce the subdir count on each platform.  Also, it gives the original
author an incentive to use the ports mechanism for all platforms that
s/he writes the package for.  In an ideal world, it would reduce the
burden of the ports maintainers and increase the number of packages
available off the bat for FreeBSD.  (Hey, one can hope, can't one?)
This would also allow FreeBSD to share ports with {Net|Open}BSD.

What do people think?

rsi
-- 
<[email protected]> a.k.a. Rajappa Iyer.   New York, New York.
        We're too busy mopping the floor to turn off the faucet.


To Unsubscribe: send mail to [email protected]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to