Re: distinguish between "core" and "main"?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/04/11 09:05, Paul Wise wrote:
> Alternatively you might want to install from testing directly. Not
> everything from testing is installable on stable, which is where
> backports comes in.
Installing testing for the whole system is no option. The base
system (the core packages) should be provided by the most recent
release. I don't want to get an unbootable system.
>
> If you install from testing directly you will need some apt pinning:
>
> http://wiki.debian.org/AptPreferences
>
> Set your /etc/apt/preferences to the below and cherry-pick packages
> from testing (or squeeze-backports/unstable/experimental). You will
> probably encounter dependency issues, conflicts and compatibility
> bugs, but apt-get upgrade will where installed, upgrade packages
> within testing. Switch to a backport to avoid those issues.
>
This sounds like a lot of manual work. I can do that for my own desktop
PC, but not for all the desktops and servers in the office.
I would prefer if Debian distinguishes between core and main instead.
This means splitting the current main repository.
In the new system the main/testing packages should be _guaranteed_
to work together with the most recent core/stable packages. Of course
they should also work together with core/testing, as they do now.
Making this scheme work would imply more frequent releases for the core
packages, but I am sure this can be done. I would expect that we would
get <1000 core packages.
Hopefully its OK if I post my ideas here? Actually this is about release
management, not about development.
Regards
Harri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk3p6PYACgkQUTlbRTxpHjdidwCfYWqYYAQIL8oiGrxb+psVX8nf
2PwAnR15E6Juy3N0p/mtbYV8y34CLw98
=Kalf
-----END PGP SIGNATURE-----
Reply to: