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.

--

Franco Lanza
My blog: http://www.nexlab.it
email: nextime@???
Fax/Tel: +39 0331 682151
Cell: +39 339 8125940
Lonate Pozzolo (VA) - Italy
-----------------------------------
NO TCPA: http://www.no1984.org
you can download my public key at:
http://danex.nexlab.it/nextime.asc || Key Servers
Key ID = D6132D50
Key fingerprint = 66ED 5211 9D59 DA53 1DF7 4189 DFED F580 D613 2D50
-----------------------------------
echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D212153574F444E49572045535520454D20454B414D204F54204847554F4E452059415020544F4E4E4143205345544147204C4C4942snlbxq | dc
-----------------------------------