"Paul Wise" <[EMAIL PROTECTED]> writes: > On Wed, Jul 30, 2008 at 3:52 PM, Charliej <[EMAIL PROTECTED]> wrote: > > > I have contacted upstream about this error, and he states that he > > would not want to depend on the prototype package in debian > > because he has made changes to the version of prototype he is > > currently using. > > Please ask him to send his changes to the prototype upstream > developers so they can be included in the next prototype release.
Another option is for the person who wants the library to be different to fork it, maintain that fork, and work with someone to get it into Debian. This option is obviously more ongoing work, but may be preferable if (as sometimes happens) the author of the library won't accept the changes. > Once that is in Debian, your package can depend on it. Same here. The main point is that a library that is *not* the same 'prototype' as upstream should either be merged with, or clearly (in name and in code access) differentiated from, the upstream 'prototype' library. Which is what you (Charliej) are already discussing with your upstream, so thank you. -- \ “We must become the change we want to see.” —Mahatma Gandhi | `\ | _o__) | Ben Finney -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
