From owner-freebsd-eclipse@FreeBSD.ORG Tue Oct 18 16:01:22 2005 Return-Path: X-Original-To: freebsd-eclipse@freebsd.org Delivered-To: freebsd-eclipse@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6670E16A41F; Tue, 18 Oct 2005 16:01:22 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from lakecmmtao06.coxmail.com (lakecmmtao06.coxmail.com [68.99.120.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id B733543D46; Tue, 18 Oct 2005 16:01:21 +0000 (GMT) (envelope-from vizion@vizion.occoxmail.com) Received: from dns1 ([64.58.171.82]) by lakecmmtao06.coxmail.com (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051018160128.SWPK17511.lakecmmtao06.coxmail.com@dns1>; Tue, 18 Oct 2005 12:01:28 -0400 From: Vizion To: freebsd-java@freebsd.org Date: Tue, 18 Oct 2005 08:56:24 -0700 User-Agent: KMail/1.8 References: <200510150015.j9F0ExKr085847@sakura.ninth-nine.com> <4354DF92.4050402@ebs.gr> <200510180730.56069.vizion@vizion.occoxmail.com> In-Reply-To: <200510180730.56069.vizion@vizion.occoxmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200510180856.27998.vizion@vizion.occoxmail.com> Cc: Wes Peters , Scot Hetzel , freebsd-ports@freebsd.org, freebsd-eclipse@freebsd.org Subject: Re: [SUGGEST] Reform eclipse and eclipse related ports X-BeenThere: freebsd-eclipse@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "FreeBSD users of eclipse EDI, tools, rich client apps & ports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 18 Oct 2005 16:01:22 -0000 On Tuesday 18 October 2005 07:30, the author Vizion contributed to the dialogue on- Re: [SUGGEST] Reform eclipse and eclipse related ports: >On Tuesday 18 October 2005 04:42, the author Panagiotis Astithas > contributed to the dialogue on- > > Re: [SUGGEST] Reform eclipse and eclipse related ports: >>Vizion wrote: >>> 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 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)? >> >>This can be done today, with an eclipse-plugins meta-port, similar to >>the php5-extensions one. I may even find some time to work on it. > >Wow > >That is great > >That is what I have been arguing for for three months!! > >david BTW If you get time would there be any chance you could set up the localized plugin archive so that it conforms with Eclipse's expectation for plugin installation. Up until now, on a multi-user system, each user has to bring plugins into their individual work directories. This has led to different users inadvertently working with different plugin versions. One of the reasons I want to get the /usr/ports/eclipse/ and /usrports/eclipse/plugins hierarchies working is to have a systenatic method of ensuring devellopers are working with identical plugin versions. The ports tree system provides an ideal method of monitoring the plugins. The other advantage of the meta-port is that we will be immediately able to bring the remaining 300 plugins into freebsd. This would be a great leap forward david > >>Cheers, >> >>Panagiotis >>_______________________________________________ >>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.