That's fine if a the one maintaining it has all the time in the world to
maintain a forked branch as each new upstream release would have then be
evaluated against the Debian patched version.
On 12/12/06, Daniel Rodriguez Garcia <[EMAIL PROTECTED]> wrote:
Hello,
As part of the open/free/peaceful/environment-friendly software
community, I'm sure we all share a common objective :)
I think the suggestions stated in previous messages may be implemented
this way:
A) Upstream code may remain untouched.
B) "acidbase" Debian package may contain a patched version of upstream
code.
C) The Debian patch may implement:
1) Remove dependencies on problematic packages, and
2.a) Completely remove graphic features, or
2.b) Conditionally remove graphic features (based on a configuration
variable), so administrator can set this "optional_graphics_available=1"
variable once she has downloaded the PEAR module and configured her PHP
installation.
In either case, Debian patch may include the corresponding
NEWS.Debian / README.Debian explaining the issue.
It is up to the Debian package maintainer's wisdom to choose the
best
approach.
Regards,
Daniel R.
