Message183495
| Author |
barry |
| Recipients |
asvetlov, barry, berker.peksag, eric.araujo, hieu.nguyen, michael.foord, pitrou |
| Date |
2013年03月04日.20:09:46 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<20130304150943.19bbfa8c@anarchist.wooz.org> |
| In-reply-to |
<1362426080.3474.0.camel@localhost.localdomain> |
| Content |
On Mar 04, 2013, at 07:45 PM, Antoine Pitrou wrote:
>
>Antoine Pitrou added the comment:
>
>> We're not going to want to install all possible flavors of
>> `pyunit2.6`, `pyunit2.7`, `punit2.6-dbg`, `pyunit-3.2-dbg`, etc. etc.
>
>Why not?
We don't know at package build time which versions will be necessary or
possible, since that depends on the user's system on which the package will be
installed. So we can't add those files to the package manifest. They could
be installed dynamically by a maintainer script (that gets triggered at
package installation time) but that's less than ideal because then we'll need
to also add machinery to properly track deletions so that when they're
dependencies get removed we can remove the scripts too. This is something
that's very much frowned upon in Debian, especially for /usr/bin scripts. |
|