Re: Integrating aptosid?
FWIW my 1 cent: the idea is really sound although a bit idealistic,
because it goes inline with my utopian future of Debian: many
derivatives are just customizations of Debian with varying level of
additional custom extensions (often DFSG-compliant thus candidates for
inclusion into Debian proper) + installer or live-media options; i.e.
they are using Debian package base and add some additional packages (or
manual installations/customizations just because it might be easier at
So at the end, is there any objective show stopper to
hypothetically have in a Debian metapackages like
N.B. couldn't come up with a good prefix, so let it be 'flavor'
installation of which would simply tune existing plain Debian
installation to actually become the derivative itself?
if only we could persuade and collaborate with derivatives authors to
make this possible and easy. Then derivative projects could concentrate
on providing custom installers/live-media and everyone would be happy.
Or am I missing some substantial design issue which is still lacking
On Tue, 03 May 2011, Pierre Habouzit wrote:
> I know it's not simple, but it's not necessarily harder than making
> testing usable, I think Joss made a pretty good case about that on his
> > Also, FYI, the aptosid development team is composed of 8 to 10 developers,
> > contributing to different things at different levels (info gathered on
> > #aptosid@OFTC).
> aptosid is just an example, I don't even know the distro, they may not
> be the best choice, I just try to find alternates ideas. Note that I
> don't think it takes more than 10 people to do the rolling distro like
> Joss propose it: snapshot unstable every month and fix the worst
> breakages. It takes more than 10 people to do the same in testing
> because each individual fix is tangled in the migration issue, hence
> rapidly needs to update things that are at first totally unrelated to be
> fixed too first.
Keep in touch www.onerussian.com
Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic