Date: Sun, 15 Feb 2004 18:30:54 +0000 From: Alex Zbyslaw <xfb52@dial.pipex.com> To: Adam Weinberger <adamw@FreeBSD.org> Cc: freebsd-ports@freebsd.org Subject: Re: mozilla-devel Message-ID: <402FBADE.10807@dial.pipex.com> In-Reply-To: <20040215170158.GE34704@toxic.magnesium.net> References: <402F9115.5040904@dial.pipex.com> <20040215164836.GD34704@toxic.magnesium.net> <1076864025.38761.2.camel@rushlight.kf8nh.com> <20040215170158.GE34704@toxic.magnesium.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Adam Weinberger wrote: > Then you can use portupgrade -o www/mozilla-devel-gtk2 mozilla-gtk2\* > when the time comes. Thanks for the suggestion but I don't think it solves the problem of *knowing* when the time comes. When the versions were different I could just do a cvsup and a portupgrade -n (suitably egreped) to figure out what needed upgrading. If I change the origin of mozilla-devel then I still won't know when it's updated -- unless I've misunderstood something. > The problem is that you can't have 2 ports with the same versions. It'll > break INDEX builds. Brandon S. Allbery KF8NH wrote: > It seems there ought to be a better way to do this; > setting the suffix to -devel and chaining to the mozilla makefile seems > to make sense.... If I understand right, Adam is saying that there can't be two ports "mozilla-1.6", but wasn't Brandon's suggestion to make the devel port called "mozilla-devel-1.6", then there aren't two ports with the same name and version? There seem to be precedents for this e.g. xemacs-devel-21.5.b15, gqview-devel-1.3.7 and others. If the port were called mozilla-devel, presumably it could either just point to mozilla, or it could duplicate it (which might make it easier to maintain when a new devel release does come along). --Alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?402FBADE.10807>