On Sun, Jul 14, 2013 at 01:26:05PM -0500, Bruce Dubbs wrote:
> Armin K. wrote:
> 
> > How about packagename-packageversion then? I personally use packagename
> > packageversion (no dash between name and version) or even a modified
> > name (ie, GStreamer Ugly Plugins instead of gst-plugins-ugly). We could
> > change remainging packages that contain spaces in their titles and
> > xrefnames to the correct packagenames if necesary.
 Sounds reasonable, but the only one that I really notice as ugly is
the one Armin highlighted.
> 
> packagename-packageversion is the most common usage.  I just went 
> through the for the entire book doing the package currency scripts. 
> There I had to use the upstream names and spelling.
> 
> There are a lot of names that I don't like:
> 
> LVM2-2.02.98
> expect5.45
> sysvinit-2.88dsf
> tcl8.6.0-src
> tzdata2013d
> iproute2-3.9.0
> boost_1_54_0

 Yeah, that last one - it looks too like debian :)

 None of the others look particularly odd to me.  Unlike the book's
debianized version of one of the libs - libcap, I think.
> 
> I also don't like the version numbers like:
> 
> shadow-4.1.5.1
> 
> Do we really need major.minor.micro.patch numbers?  Three should be all 
> that's needed.
> 
 I don't see any problem there, I guess we have different ideas of
taste.  Old packages such as dhcp are similar, but hardcoding a P
instead of the last '.'
> Some versions have just gone to a sequential number:
> 
> kmod-14
> systemd-205
> 
> But that's OK.
> 
> If it were up to me, I'd change a lot of these names, but it is really 
> up to the developers so it's not my call.
> 
> For BLFS, we need to be consistent with upstream.  That said, I don't 
> want to make a special effort to change the book right now.  Changing 
> the entries as the packages are updated is OK with me.
> 
>    -- Bruce

 For the changelog, I don't see any problem with specifying
somename-1.2.3 even if the tarball is somename1.2.3 or
somename-1.2.3xyz or somename_1_2_3.  But this is all close to
bikeshedding.  I can live with each editor using a different
convention, and changing how they record these in the changelog from
one day to the next.

ĸen
-- 
das eine Mal als Tragödie, das andere Mal als Farce
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to