From owner-freebsd-ports@FreeBSD.ORG Tue Oct 18 01:04:51 2005 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B3E716A41F for ; Tue, 18 Oct 2005 01:04:51 +0000 (GMT) (envelope-from neuhauser@sigpipe.cz) Received: from isis.sigpipe.cz (fw.sigpipe.cz [62.245.70.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id 488C143D46 for ; Tue, 18 Oct 2005 01:04:50 +0000 (GMT) (envelope-from neuhauser@sigpipe.cz) Received: by isis.sigpipe.cz (Postfix, from userid 1001) id 1C9FB1F87BFD; Tue, 18 Oct 2005 03:04:47 +0200 (CEST) Date: Tue, 18 Oct 2005 03:04:46 +0200 From: Roman Neuhauser To: Scot Hetzel Message-ID: <20051018010446.GH71766@isis.sigpipe.cz> Mail-Followup-To: Scot Hetzel , Wes Peters , freebsd-ports@freebsd.org, kris@obsecurity.org References: <200510150015.j9F0ExKr085847@sakura.ninth-nine.com> <20051015053003.GB28137@soaustin.net> <4350CE50.8080704@ebs.gr> <5739E97B-7EDC-4971-9EA5-01A44688A981@softweyr.com> <43522953.6050700@ebs.gr> <1B8112AF-8C0E-4BA0-8D1C-DA6AD529F327@softweyr.com> <20051017153024.GA23494@arabica.esil.univ-mrs.fr> <20051017212748.GD71766@isis.sigpipe.cz> <790a9fff0510171505i4010cc05yc30f67d459d1a0e4@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <790a9fff0510171505i4010cc05yc30f67d459d1a0e4@mail.gmail.com> User-Agent: Mutt/1.5.9i Cc: Wes Peters , freebsd-ports@freebsd.org, kris@obsecurity.org Subject: Re: [SUGGEST] Reform eclipse and eclipse related ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2005 01:04:51 -0000 # swhetzel@gmail.com / 2005-10-17 17:05:18 -0500: > On 10/17/05, Roman Neuhauser wrote: > > Wes said: "I have to resort to 'make search'" which presumably means > > he'd prefer to just ls /usr/ports/$emacs_category; while 'make > > search' is a bearable interface (FMPOV), you can't beat a ls. > > > > Hey, what about materialized virtual categories? A bunch of > > symlinks, and everyone's happy. Or is that too much for CVS? > > It would probably be too much for CVS to handle, instead someone could > modify bsd.port.mk to create the virtual category directories and then > symbolicly link the ports into these categories. > > The following could be added to bsd.port.mk > > virtualport: > .for CATEGORY in ${CATEGORIES} > .if not exist ${PORTSDIR}/${CATEGORY} > mkdir ${PORTSDIR}/${CATEGORY} > .endif > .if not exist ${PORTSDIR}/${CATEGORY}/${PORTNAME} > ln -s ${.CURDIR} ${PORTSDIR}/${CATEGORY}/${PORTNAME} > .endif > .endfor > > which would add the link for a specific port. The we would need to > add a virtualports target (bsd.subdir.mk?) that would decend thru all > the ports creating all the symbolic links (similar to the "make > readmes" target used in /usr/ports/ ). > > Also there would need to be another target that would remove all the > symbolic links, that way you could re-create them without worrying > about removed symbolic links pointing to non-existant ports. > > NOTE: Non of this code has been tested. If you want this feature, work > on improving the code and submitting it as a patch to the PR database > for Ports Managers to accept/reject. I'm putting this in my .plan, and will eventually work on it unless someone points me at a past discussion that showed there were major technical obstacles to this. I think I could manage inside /usr/ports/Mk: * create an update-vcats that works in all of portsdir, portsdir/category and portsdir/category/port * maintain a list of names of virtual categories in a make variable * create symlinks in the virtual categories this port lists in CATEGORIES * delete symlinks to this port from other virtual categories if any But I'm quite concerned about the changes needed to make things like the package building cluster or make index aware of this. It looks like it would have quite far reaching consequences. Kris? -- How many Vietnam vets does it take to screw in a light bulb? You don't know, man. You don't KNOW. Cause you weren't THERE. http://bash.org/?255991