cvs commit: ports/devel/libglademm24 Makefile distinfo pkg-plist

Adam Weinberger adamw at FreeBSD.org
Sat Mar 12 09:14:14 PST 2005


Remko Lodder wrote:
> Joe Marcus Clarke wrote:
> 
>> marcus      2005-03-12 11:27:59 UTC
>>
>>   FreeBSD ports repository
>>
>>   Modified files:
>>     devel/libglademm24   Makefile distinfo pkg-plist   Log:
>>   Update to 2.6.0.  Note: this release is API and ABI compatible with
>>   2.4.x, so a repocopy to libglademm26 is not needed.
>>     Revision  Changes    Path
>>   1.15      +12 -4     ports/devel/libglademm24/Makefile
>>   1.8       +2 -2      ports/devel/libglademm24/distinfo
>>   1.5       +5 -6      ports/devel/libglademm24/pkg-plist
> 
> 
> Doesn't the directory name make it more confusing then?
> Since if i enter /usr/ports/devel/libglademm24 i expect
> a 2.4 release and not a 2.6, this makes it a bit confusing
> perhaps for others.
> 
> Isn't it a idea to make these directory's more global?
> like /usr/ports/devel/libglademm2 (to refer to the 2.x versions) ?
> 
> this goes for all the latest commits that had this update :)
> 
> cheers,
> 

I *VERY* much agree with you on this. We made our lives much more 
difficult by putting GNOME 2.0 into portname2. Now, we have a bunch of 
portname2's, without portname ports. IMO we should be denoting the 
stable version of something by not qualifying it with a number. I mean, 
if a user or porter needs to depend upon gtkmm, they'll say, "I need 
gtkmm. I better use x11-toolkits/gtkmm." But if they have to have 
gtkmm-2.2 and nothing else, THEN they can qualify it with "I need 
x11-toolkits/gtkmm22."

And for that matter, I *really* think it's time to move 
x11-toolkits/gtk--2 (which installs stuff named gtkmm) into 
x11-toolkits/gtkmm.

# Adam


-- 
Adam Weinberger
adamw at magnesium.net || adamw at FreeBSD.org
adamw at vectors.cx    ||   adamw at gnome.org
http://www.vectors.cx


More information about the cvs-ports mailing list