On Thu, 2006-05-11 at 00:24:20 -0700, Erast Benson wrote:
> On Fri, 2006-05-12 at 01:49 +0300, Guillem Jover wrote:
> > On Tue, 2006-04-11 at 19:42:21 -0700, Erast Benson wrote:
> > > And we need 2.11, to distinguish 8,7,9,10,11,12 releases.
> > > But I guess, presented dpkg-architecture.pl patch should take care..
> > > So, yes this might work, but not always (see below)
> > 
> > Why do you need the 2.11, would another release imply a new Debian
> > architecture, are the kernels incompatible, the libc etc?
> > And I don't see anything relevant below.
> 
> Correct, Debian architecture doesn't care. But, applications do care.
> For instance, things might be layout differently in 2.10 and upcoming
> 2.11 architectures, which might need required for some apps to do things
> a bit differently too. So, it is not about Debian architecture, it is
> all about how we will affect existing apps. We obviously don't want fix
> all existing apps, instead we want just tune up Debian architecture
> parameters once and for all.

What do you mean with "things might be layout differently", can you
give a concrete example?

If those apps are using autoconf they will use the real gnu triplet,
and not the ones provided by dpkg-architecture. I suppose the problem is
that I cannot see how the 2.xx minor release can affect the packaging.

> > > but we expect:
> > >
> > > sparc-sun-solaris2.11

> > Well if config.guess is producing unwanted output, you should be
> > fixing it instead of working it around in all other programs.
> 
> I think we've got disconnected on this one. config.guess often shipped
> withing app itself as a hard copy, so it will not be possible to fix
> autoconf package for all.

> Any other solutions?

Mass updating config.guess and config.sub are the common practice,
we've done that in Debian for example for the GNU/kFreeBSD port, it
didn't have any triplet some years ago, we just added it to config.*
as the first thing and then started with the port, with time apps got
updated, announce mails were sent so that people would update the
files themselves and the ones that didn't after a while got bug
reports with requests to update. (Another recent port added to the
triplet could be amd64).

regards,
guillem



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to