Re: Sparc release requalification

2009-08-20 Thread Bastian Blank
On Thu, Aug 20, 2009 at 07:09:44AM +0200, Mike Hommey wrote:
 On Wed, Aug 19, 2009 at 04:33:32PM +0200, Bastian Blank wrote:
  If I understand this correctly, this would need the modification off all
  library packages to implement biarch semantic.
 ... which will be needed anyways. So your choice is actually between
 doing it and doing it plus some extra intermediate work.

No, we don't need to do that. Thats what is multiarch for.

Bastian

-- 
Captain's Log, star date 21:34.5...


-- 
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: Sparc release requalification

2009-08-20 Thread Philipp Kern
On Thu, Aug 20, 2009 at 10:45:46AM +0200, Bastian Blank wrote:
 On Thu, Aug 20, 2009 at 07:09:44AM +0200, Mike Hommey wrote:
  On Wed, Aug 19, 2009 at 04:33:32PM +0200, Bastian Blank wrote:
   If I understand this correctly, this would need the modification off all
   library packages to implement biarch semantic.
  ... which will be needed anyways. So your choice is actually between
  doing it and doing it plus some extra intermediate work.
 No, we don't need to do that. Thats what is multiarch for.

It's not intended that multiarch supports switching architectures.  Of course
it would help to import some 64bit packages selectively from a sparc64 port
but most of your binaries would still be 32bit with the only partially supported
code generation?  Even on a rebuild you would have to pull in the 64bit
libs in a way you build against them by default?  (Or would that boil down
to passing another DEB_*_ARCH so that config.guess targets 64bit and stuffing
that into simple packages with arch:sparc?)

Kind regards,
Philipp Kern
-- 
 .''`.  Philipp KernDebian Developer
: :' :  http://philkern.de Stable Release Manager
`. `'   xmpp:p...@0x539.de Wanna-Build Admin
  `-finger pkern/k...@db.debian.org


signature.asc
Description: Digital signature


Re: Sparc release requalification

2009-08-20 Thread Matthias Klose

On 19.08.2009 16:33, Bastian Blank wrote:

On Wed, Aug 19, 2009 at 01:55:24PM +0200, Matthias Klose wrote:

On 19.08.2009 13:42, Bastian Blank wrote:

On Wed, Aug 19, 2009 at 01:16:36PM +0200, Matthias Klose wrote:

I did speak with Martin Zobel at Debconf on how to get there, having two 
proposals:
   - have an inplace-transition building required library packages for an
 upgrade as biarch packages and continue to use the current sparc name.

This would mean that many packages needs to be modified. Is it really
worth the work needed if we consider the availability of multiarch in
the next time?

you'll end up modifying a different set of packages for the new
architecture name in control and rules files. I don't know if this is
less or more work.


If I understand this correctly, this would need the modification off all
library packages to implement biarch semantic.


No, just a subset that an update from 32-64bit userland does work. Again, I 
don't know how big this subset will be.


  Matthias


--
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: Sparc release requalification

2009-08-20 Thread Aurelien Jarno
Bastian Blank a écrit :
 On Wed, Aug 19, 2009 at 01:16:36PM +0200, Matthias Klose wrote:
 I did speak with Martin Zobel at Debconf on how to get there, having two 
 proposals:
  - define a new sparc64 port, and bootstrap this one using the 32bit port.
 
 This is rather easy. I already did a s390x bootstrap using this method.
 

If we are not sure that sparc and s390 (ie 32-bit versions) would be
suitable for squeeze, this is almost sure they won't be suitable for
squeeze+1.

Isn't it the right moment to start a sparc64 and an s390x port, and if
they are ready for squeeze release with them? Almost whatever upgrade
solution you offer will require to have at least one release with both
old and new architecture (like we did for arm - armel).

Given that we already have sparc and s390 in the archive and that we
also already have 64-bit ports, I don't expect any major problem for
those new ports. Also given quite fast hardware exists for those
architectures, it can probably be done relatively quickly.

-- 
Aurelien Jarno  GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net


-- 
To UNSUBSCRIBE, email to debian-s390-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org