On Tue, Mar 11, 2014 at 10:30:13PM -0500, Bruce Dubbs wrote: > > The naming of files is also quite inconsistent. For example, we have > junit4_4.11.orig.tar.gz. First why do they need to tell us it's version > 4 twice. Second, why do they need to add 'orig'. What else would it > be? Binary? If so, then for what architecture? Actually junit is java > and you don't have binaries. > Standard debian (and its derivatives, in this case ubuntu) - they probably have a policy for it, along with the underscore in the name. Remember that debian has some very old versions of certain packages, and that different packages may depend on either the old or the new versions. So in this case, it's like libcap which they named as libcap2 when we were using them for the source.
The 4.11 tells us the actual version. The '.orig' confirms it is upstream (sometimes there is an abbreviation dfsg (debian free software guidelines) which I _believe_ indicates that certain parts of the source have been removed for licencing issues. Depending on the age of the package, sometimes there is also a '.debian.tar.gz' which contains the debian files for modifying their build system, as well as patches, changelog, list of files installed, etc. Their binaries are normally packaged as _*.deb files, with an indication of the architecture such as amd64, armel, armhf, i386, ia64, mips, mipsel, powerpc, s390, sparc and perhaps some other linux arches, as well as the non-linux. in the case of java the binary is _all.deb : for debian itself, junit is still at 3.8.2. ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
