Date: Mon, 17 Oct 2005 15:22:14 -0700 From: Vizion <vizion@vizion.occoxmail.com> To: freebsd-ports@freebsd.org Cc: freebsd-java@freebsd.org, Wes Peters <wes@softweyr.com>, Scot Hetzel <swhetzel@gmail.com>, freebsd-eclipse@freebsd.org Subject: Re: [SUGGEST] Reform eclipse and eclipse related ports Message-ID: <200510171522.17180.vizion@vizion.occoxmail.com> In-Reply-To: <790a9fff0510171505i4010cc05yc30f67d459d1a0e4@mail.gmail.com> References: <200510150015.j9F0ExKr085847@sakura.ninth-nine.com> <20051017212748.GD71766@isis.sigpipe.cz> <790a9fff0510171505i4010cc05yc30f67d459d1a0e4@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 17 October 2005 15:05, the author Scot Hetzel contributed to the
dialogue on-
Re: [SUGGEST] Reform eclipse and eclipse related ports:
>On 10/17/05, Roman Neuhauser <neuhauser@sigpipe.cz> 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.
>
>Scot
Would this provide an opportunity to have for example:
/usr/ports/eclipse
/usr/ports/eclipse/plugins/
so that the plugins could be selected for installation from make config
in /usr/ports and manage the installation of the plugins (rather similar to
what happens for php)?
david
>--
>DISCLAIMER:
>No electrons were mamed while sending this message. Only slightly bruised.
>_______________________________________________
>freebsd-ports@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
--
40 yrs navigating and computing in blue waters.
English Owner & Captain of British Registered 60' bluewater Ketch S/V Taurus.
Currently in San Diego, CA. Sailing bound for Europe via Panama Canal after
completing engineroom refit.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200510171522.17180.vizion>