Re: Bug#396365: please add a gdb .udeb, for easier debugging inside d-i

[Otavio Salvador <otavio@debian.org>]

Sven Luther <sven.luther@wanadoo.fr> writes:

>> >> The biggest problem here is that will looks like we'll support all
>> >> those combinations regarting security and also bug fixing and this
>> >> won't be true... that can be used if it stay just as a sid resource...
>> >
>> > Since the problem of moving versions only appears during the development phase
>> > of a release, not once it is released, this is indeed no problem at all.
>> >
>> > Please go ahead and try to do a beta3 netboot install right now, it will have
>> > trouble since we can't have 2.6.15 or whatever it was, and 2.6.17 kernel
>> > modules in the archive at the same time. Not easily anyway.
>> 
>> Yes. I know it'll fail.
>> 
>> I see the problem you're trying to address ... I just not sure if it's
>> the right way to solve it.
>
> Do you see another way ? I mean, sure doing nothing and ignoring the issue is
> another way to address the issue, but somehow that is not very satisfying.

Maybe the installer kernel would have the release version on the
package name and then it wouldn't be remove from the suite until the
next version. e.g:

 - linux-image-d-i-4.0-rc1

It would make sure that all udebs would be available until we move
the:

 - linux-image-d-i-4.0-rc2

 or 

 - linux-image-d-i-4.0-release

In that way we don't need to support a lot of images but just the
current and the next one while doing the development on sid. Keep on
mind that we don't have two major kernel versions anymore and then it
would be easy to do. It would work basically as other core components
like GCC or XEN.

-- 
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: otavio@debian.org      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
---------------------------------------------
"Microsoft gives you Windows ... Linux gives
 you the whole house."