From owner-freebsd-ports Mon Oct 5 02:18:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA08122 for freebsd-ports-outgoing; Mon, 5 Oct 1998 02:18:41 -0700 (PDT) (envelope-from owner-freebsd-ports@FreeBSD.ORG) Received: from xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.43.201]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA08099 for ; Mon, 5 Oct 1998 02:18:29 -0700 (PDT) (envelope-from nordwick@xcf.berkeley.edu) Received: (qmail 1336 invoked from network); 5 Oct 1998 09:19:43 -0000 Received: from ip40.san-francisco22.ca.pub-ip.psi.net (HELO yasmeen) (38.28.60.40) by scam.xcf.berkeley.edu with SMTP; 5 Oct 1998 09:19:43 -0000 Message-ID: <008d01bdf040$570af130$283c1c26@yasmeen.citycom.com> From: "Jason Nordwick" To: Subject: A few ports/pkg_* questions. Date: Mon, 5 Oct 1998 02:12:55 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org After using FreeBSD for a while and loving the ports collections, I had a few questions why things are done the way they are: 1) Why is /usr/ports so flat? It is basically /usr/ports//. This was fine when the number was low, but now after a few thousand, this is getting kinda hard to lookat. Instead of having all /usr/ports/x11-{,clocks,fm,fonts,toolkits,wm} why is it not /usr/ports/x11/{,clocks,fm,fonts,toolkits,wm} ? It is just to make the Makefiles simplier? 2) Why not links? (maybe there are and I just dont see them, this is a strong possibility). It seems that port can be in more than one category. 3) Has anybody ever thought of installing a port in is own directory and then linking them into the proper place? 4) more complete (dare I say it... robu..., ack) package tool. For operation like determining what file belongs to what, and some other common tasks I hear people talk about. 5) redoing the pkg stuff to have more complex information. I can't remember my wishlist I used to have (especially after helping do a few ports), but I can remember one: When a package/port has other ports that it could take advantage of asking to build them with an explanation of why. I know almost all scenarios could be done with a comprehensive install script, but once more than a few ports need something like that it would seem to be worth adding to the package stuff. Also, then you could register a script to be run when that other port is deinstalled (so it could change a config file somethere and such). Or maybe it could watch for a port to be installed to take advantage of. Im sure others have ideas. Just wondering if any of these have ever been talked about, sorry for my ignorance, Jay -- 4.4 > 98 http://www.xcf.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message