I've searched the lintian lab for debhelper config files
containing ${ -- found none.
Now, when designing an interface like this, I like to try to think a
little bit ahead. Will arbitrary environment variables being expanded
in these files be abused? Will it make packages that are harder
for others to maintain, or that are less fragile, or harder to
source-introspect in useful ways? What is the escaping mechanism when
someone needs to put ${ literally in later? Perhaps only a subset of
environment variables, like DEB_* should be expanded? Are environment
variables the right thing at all -- perhaps debhelper should just look
up DEB_HOST_MULTIARCH on its own, and only fill that in? These are
some of the things I have been slowly mullting over; after developing
debhelper for 15 years, I have learned to think about this stuff first
rather than deal with getting it wrong later.
1 Mar 15 Ubuntu Merge-o- Ubuntu debhelper 8.1.2ubuntu2
I have a new policy: Once Ubuntu applies a patch to software I wrote,
without allowing me to sign off on it[1], I will no longer apply that
patch to the upstream source of the package. By doing this, over and over
again, Ubuntu is implicitly saying that they do not value my work, my
expertese, or the time I would need to spend to deal with fallout of
their changes, and so I simply choose to ignore them in return.
So, if Debian feels it is appropriate for this bug to be fixed,
someone will need to NMU debhelper.
--
see shy jo
[1] security fixes and grave bugfixes excluded
signature.asc
Description: Digital signature
