Re: distinguish between "core" and "main"?
-----BEGIN PGP SIGNED MESSAGE-----
On 06/07/11 00:59, Russ Allbery wrote:
> Harald Dunkel <firstname.lastname@example.org> writes:
>> Not exactly. I would like to get a stable build and runtime environment
>> for the packages in main/testing.
> Yes, that's what I'm saying doesn't actually exist. There isn't, in
> Debian, such a thing as a "build and runtime environment" that's separate
> from the packages. The packages *are* the build and runtime environment.
There already is: Debian is shipping a "stable" gcc/g++ in parallel
to an up-to-date version, for example. My suggestion is to extend
this scheme, and to keep these packages separate from the current
> It's kind of like asking for walls separate from your house.
Its more like keeping the basement stable, while building new
walls on top of it.
> More just irrelevant. It doesn't matter whether the core is
> self-contained for what you're proposing. The problem is that the
> packages that you want to run depend on newer versions of the packages
> that you consider core, for basically any useful definition of "core."
I do not see that. All packages were available at build time in
the right version. Where should this broken dependency come from,
unless you are ignoring dependencies on promoting packages from
unstable to testing to stable?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----