Date: Tue, 20 Mar 2012 07:20:52 -0500 From: Chuck Burns <break19@gmail.com> To: freebsd-current@freebsd.org Subject: Re: ABI/architecture identification for packages Message-ID: <4F687624.9090604@gmail.com> In-Reply-To: <CAPJF9wkWFs46mh4BSXjxkyw-c6qV3FiChBC_PLE4Oj-EtKnxig@mail.gmail.com> References: <20120319213508.GA1692@azathoth.lan> <20120320091935.GF1692@azathoth.lan> <20120320102008.GH2358@deviant.kiev.zoral.com.ua> <CAPJF9wkWFs46mh4BSXjxkyw-c6qV3FiChBC_PLE4Oj-EtKnxig@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
We should probably pad the version number, and shorten things up.. similar to: package-1.2-fbsd09.1-x86.pkg package-1.2-fbsd09.1-x64.pkg package-1.2-fbsd09.1-ppc.pkg package-1.2-fbsd09.1-ppc64.pkg package-1.2-fbsd09.1-arm.pkg For app "Package" version 1.2, on FreeBSD 9.1 drop the .1 for .0 versions. The reason for the padding is to help with sorting, at least until freebsd 100.0 comes out. :P Chuck Burns On 3/20/2012 5:40 AM, Alexander Yerenkow wrote: > IMHO, > 32 / 64 = easily parsable and represent integer. > > i386/amd64 - wellknown names, but this info about processor bits not lies > in math. > My point is i386 is arch, so can be kept, while 32 is processor bit count. > If you'll keep 32/64 various checks in side software will be simple (if you > have 32 bit processor, then this info is bundled in "32"), > while if you consider using "i386" string as storage of information about > "32" bit, it not so elegant. > Also, linuxes has come to i386- i586- i686- mess, and many their scripts > looks overbloated when they checks if system really 32 bit. > > Just my point of view :) > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F687624.9090604>