Franco Lanza wrote:
> On Mon, Dec 01, 2014 at 12:44:46AM -0500, Miles Fidelman wrote:
>> I think it has to go deeper than that. This has to happen in the installer,
>> before pinning comes into play. That means some combination of:
>> - metadata in the repo (i.e., not marking any systemd component as
>> essential)
>> - modifying the installer, or at least the installer configuration
>> - fixing debootstrap (the patch to bug #668001) so that -include and
>> -exclude statements work properly
>>
>> That would seem the place to start.
>>
>> And right after that, going through the Debian repo to find any package with
>> a dependency that leads back to systemd (or one of its relatives), and
>> recompiling & repackaging it to depend on either:
>> - something else, and/or
>> - a metapackage that defaults to something else (and creating that
>> metapackage, if necessary)
>>
>
> This is exactly the path we are following right now.
>

Cool!

Miles Fidelman

--
In theory, there is no difference between theory and practice.
In practice, there is. .... Yogi Berra