You are not logged in.

#1 2007-08-27 01:06:10

dale77
Member
From: Down under
Registered: 2007-02-10
Posts: 102
Website

Package versions

What's with this package version:

gcc 4.2.1-3.1

Why -3.1 instead of -4?

Just asking because if we ever do deltas the code will have to handle these weird package point releases.

Thanks

Dale

Last edited by dale77 (2007-08-27 01:06:31)

Offline

#2 2007-08-27 01:14:25

tardo
Member
Registered: 2006-07-15
Posts: 526

Re: Package versions

.1 is specific to x86_64.

Offline

#3 2007-08-27 05:43:01

dale77
Member
From: Down under
Registered: 2007-02-10
Posts: 102
Website

Re: Package versions

So as an i686 user I won't be bothered with it then?

Why not gcc-4.2.1-4-x86_64.pkg.tar.gz? Some backward compatibility thing?

Not quite getting it...

Offline

#4 2007-08-27 05:51:36

tardo
Member
Registered: 2006-07-15
Posts: 526

Re: Package versions

as far as I know, if a rebuild is required specifically for x64, then there isn't a need to bump pkgrel. just suffixing with .# was what the devs apparently agreed on. besides, if i686 was left at -3, and x64 went to -4, this might cause confusion in the future...

and yes, non x64 users need not be bothered.

Last edited by tardo (2007-08-27 05:51:52)

Offline

#5 2007-08-27 10:11:56

dale77
Member
From: Down under
Registered: 2007-02-10
Posts: 102
Website

Re: Package versions

pacman -Syu still downloads the -3.1 release to my i686 system, notwithstanding the change is x86_64 specific.

I think I would prefer they just call it -4. This point release business doesn't seem to be adding a whole lot of value.

What is the practical difference between an architecture specific fix and a fix for both architectures?

Last edited by dale77 (2007-08-27 10:17:52)

Offline

#6 2007-08-27 11:32:16

shining
Pacman Developer
Registered: 2006-05-10
Posts: 2,043

Re: Package versions


pacman roulette : pacman -S $(pacman -Slq | LANG=C sort -R | head -n $((RANDOM % 10)))

Offline

#7 2007-08-28 00:52:12

dale77
Member
From: Down under
Registered: 2007-02-10
Posts: 102
Website

Re: Package versions

Thanks for that link to the thread.

So the aim is for i686 not to have to rebuild/download their package when x86_64 make their x86_64 specific mods?

It looks like the "download" part of that aim is not working today, as I had to pull down gcc-4.2.1-3.1 yesterday. I'll need to check that mine was definitely an "upgrade" from 4.2.1-3 to -3.1 though.

How does it go today I wonder?

1. i686 releases -3
2. x86_64 get the PKGBUILD and hack it a bit for their arch
3. x86_64 release a -3.1 so that the build system churns out a 64bit pkg, but i686 remains at -3?

hmm

Offline

#8 2007-08-28 00:59:56

Cerebral
Forum Fellow
From: Waterloo, ON, CA
Registered: 2005-04-08
Posts: 3,108
Website

Re: Package versions

The same can work in reverse.   

1) i686 releases -3
2) x86_64 releases -3
3) i686 realizes there was a problem with their build of -3 (for example, debugging symbols accidentally left in, as was the case for gcc)
4) i686 releases -3.1

Just for the record, I don't like the decimal pkgrel versions either.

Offline

Board footer

Powered by FluxBB