On Wed, Mar 21, 2012 at 05:18:07PM +0200, Vitaly Magerya wrote:
> Baptiste Daroussin wrote:
> > when a package can be installed in both i386 and amd64
> >
> > and maybe in the Makefile:
> >
> > PKGARCH=i386 amd64
> >
> > or
> >
> > PKGARCH=x86:32 x86:64
>
> Baptiste, if ABI/arch ids wi
On Wed, Mar 21, 2012 at 03:59:38PM +0100, Alexander Leidinger wrote:
> Quoting Baptiste Daroussin (from Wed, 21 Mar 2012
> 14:59:20 +0100):
>
> > On Wed, Mar 21, 2012 at 02:34:03PM +0100, Alexander Leidinger wrote:
> >> Quoting Bruce Cran (from Tue, 20 Mar 2012
> >> 14:26:42 +):
> >>
> >
Baptiste Daroussin wrote:
> when a package can be installed in both i386 and amd64
>
> and maybe in the Makefile:
>
> PKGARCH= i386 amd64
>
> or
>
> PKGARCH= x86:32 x86:64
Baptiste, if ABI/arch ids will leak out to port Makefiles (i.e. I will
need to care about them), then please lea
Quoting Baptiste Daroussin (from Wed, 21 Mar 2012
14:59:20 +0100):
On Wed, Mar 21, 2012 at 02:34:03PM +0100, Alexander Leidinger wrote:
Quoting Bruce Cran (from Tue, 20 Mar 2012
14:26:42 +):
> On 20 Mar 2012, at 10:20, Konstantin Belousov wrote:
>
>> i386-32 and amd64-64 is weird and
On Wed, Mar 21, 2012 at 02:34:03PM +0100, Alexander Leidinger wrote:
> Quoting Bruce Cran (from Tue, 20 Mar 2012 14:26:42 +):
>
> > On 20 Mar 2012, at 10:20, Konstantin Belousov wrote:
> >
> >> i386-32 and amd64-64 is weird and confusing.
> >>
> >> IMO, you should go either with x86-{32,64} n
Quoting Bruce Cran (from Tue, 20 Mar 2012 14:26:42 +):
On 20 Mar 2012, at 10:20, Konstantin Belousov wrote:
i386-32 and amd64-64 is weird and confusing.
IMO, you should go either with x86-{32,64} names, or with i386/amd64,
not with a mix.
Would we ever want to support something like x3
On Tue, Mar 20, 2012 at 05:18:12PM +0200, Andriy Gapon wrote:
> on 20/03/2012 16:39 Baptiste Daroussin said the following:
> > On Tue, Mar 20, 2012 at 07:20:52AM -0500, Chuck Burns wrote:
> >> We should probably pad the version number, and shorten things up..
> >> similar to:
> >>
> >> package-1.2
on 20/03/2012 16:39 Baptiste Daroussin said the following:
> On Tue, Mar 20, 2012 at 07:20:52AM -0500, Chuck Burns wrote:
>> 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-
On Tue, Mar 20, 2012 at 02:26:42PM +, Bruce Cran wrote:
>
> On 20 Mar 2012, at 10:20, Konstantin Belousov wrote:
>
> > i386-32 and amd64-64 is weird and confusing.
> >
> > IMO, you should go either with x86-{32,64} names, or with i386/amd64,
> > not with a mix.
>
> Would we ever want to sup
On Tue, Mar 20, 2012 at 07:20:52AM -0500, Chuck Burns wrote:
> 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-ar
On 20 Mar 2012, at 10:20, Konstantin Belousov wrote:
> i386-32 and amd64-64 is weird and confusing.
>
> IMO, you should go either with x86-{32,64} names, or with i386/amd64,
> not with a mix.
Would we ever want to support something like x32 from Linux (which might be
amd64-32)?
http://www.linu
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 vers
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
On Tue, Mar 20, 2012 at 10:19:36AM +0100, Baptiste Daroussin wrote:
> On Mon, Mar 19, 2012 at 10:35:08PM +0100, Baptiste Daroussin wrote:
> > Hi all,
> >
> > In order to identify architectures I need to find a uniq id for every
> > possibilities (for pkgng)
> >
> > here is the identification I pr
On Mon, Mar 19, 2012 at 10:35:08PM +0100, Baptiste Daroussin wrote:
> Hi all,
>
> In order to identify architectures I need to find a uniq id for every
> possibilities (for pkgng)
>
> here is the identification I propose:
>
> arch-class-os-majorversion(-archi_specific_extension)
>
> arch can be
On Tue, Mar 20, 2012 at 06:24:37AM +, Poul-Henning Kamp wrote:
> In message <20120319215802.gc1...@azathoth.lan>, Baptiste Daroussin writes:
>
> >On Mon, Mar 19, 2012 at 10:35:08PM +0100, Baptiste Daroussin wrote:
> >> Hi all,
> >>
> >> In order to identify architectures I need to find a uniq
Hello.
On 03/20/2012 10:24, Poul-Henning Kamp wrote:
In message<20120319215802.gc1...@azathoth.lan>, Baptiste Daroussin writes:
On Mon, Mar 19, 2012 at 10:35:08PM +0100, Baptiste Daroussin wrote:
here is the identification I propose:
arch-class-os-majorversion(-archi_specific_extension)
Gi
In message <20120319215802.gc1...@azathoth.lan>, Baptiste Daroussin writes:
>On Mon, Mar 19, 2012 at 10:35:08PM +0100, Baptiste Daroussin wrote:
>> Hi all,
>>
>> In order to identify architectures I need to find a uniq id for every
>> possibilities (for pkgng)
>>
>> here is the identification I
On Mon, Mar 19, 2012 at 5:41 PM, Nathan Whitehorn
wrote:
> On 03/19/12 14:35, Baptiste Daroussin wrote:
>>
>> Hi all,
>>
>> In order to identify architectures I need to find a uniq id for every
>> possibilities (for pkgng)
>>
>> here is the identification I propose:
>>
>> arch-class-os-majorversio
On 03/19/12 14:35, Baptiste Daroussin wrote:
Hi all,
In order to identify architectures I need to find a uniq id for every
possibilities (for pkgng)
here is the identification I propose:
arch-class-os-majorversion(-archi_specific_extension)
arch can be one of the following:
- x86 for i386 an
On 19/03/2012 22:04, Baptiste Daroussin wrote:
> On Mon, Mar 19, 2012 at 06:01:23PM -0400, Eitan Adler wrote:
>> On Mon, Mar 19, 2012 at 5:35 PM, Baptiste Daroussin wrote:
>>> Hi all,
>>>
>>> In order to identify architectures I need to find a uniq id for every
>>> possibilities (for pkgng)
>>>
>>
On Mon, Mar 19, 2012 at 06:01:23PM -0400, Eitan Adler wrote:
> On Mon, Mar 19, 2012 at 5:35 PM, Baptiste Daroussin wrote:
> > Hi all,
> >
> > In order to identify architectures I need to find a uniq id for every
> > possibilities (for pkgng)
> >
> > arch-class-os-majorversion(-archi_specific_exten
On Mon, Mar 19, 2012 at 5:35 PM, Baptiste Daroussin wrote:
> Hi all,
>
> In order to identify architectures I need to find a uniq id for every
> possibilities (for pkgng)
>
> arch-class-os-majorversion(-archi_specific_extension)
>
> os will always be freebsd :) (lower case)
So why bother?
--
On Mon, Mar 19, 2012 at 10:35:08PM +0100, Baptiste Daroussin wrote:
> Hi all,
>
> In order to identify architectures I need to find a uniq id for every
> possibilities (for pkgng)
>
> here is the identification I propose:
>
> arch-class-os-majorversion(-archi_specific_extension)
>
> arch can be
24 matches
Mail list logo
