-=| Gabor Szabo, Sun, Feb 15, 2009 at 09:47:40AM +0200 |=- > On Sat, Feb 14, 2009 at 1:20 PM, Damyan Ivanov <dmn@debian.org> wrote: > > There were a couple of dependencies that were not sufficiently new > > in > > Debian, but it seems nothing breaks when using the versions from > > Debian so I have relaxed the version requirements. > > That would be an important piece of information to relay to the > original developers > in *every case* for several reasons. > > 1) with bugs most users will come to complain to the original > developers and not the > Debian maintainers, the original developers should be aware of this issue. I disagree with the first part, but still agree with the second. > 2) The original developers might be aware of a situation when you do > need the advanced version. > 3) If the package really does not need such an advanced version of a > dependency it > could be relaxed in general not just for Debian. Agreed.. > This is just a special case of Debian patching upstream packages. > Please avoid it > and try to communicate any such patch to the upstream developers. I did, actually for all patches I thought would be relevant outside Debian (remember the streamlet of tickets). Anyway, I'll look at all the changes and send a summary to padre-dev. > Padre Plugins > > Now that Padre is getting closer to inclusion, could you also start looking > at the Plugins? As the Plugins themself might also be quickly moving target > and as they are pure perl packages - hence easy to install - we have created > a "Task" that will list all the dependencies of the plugins. I have no immediate plan for packaging any plugin yet. Sorry, my time is rather limitted lately. As you see, packaging padre already needed regular nagging :) What I am generally concerned of is compatibility between plugins and Padre. Will old plugins continue to run with newer Padre? How stable is the plugin API? > We created that especially for downstream packages to make it easier for them > to package the dependencies of the Padre Plugins. > If you can include most of those as .deb packages that will make the life of > our users much easier. > http://search.cpan.org/dist/Task-Padre-Plugin-Deps/ It would be sufficient if each plugin declares its own dependencies (which I assume they do). -- dam JabberID: dam@jabber.minus273.org
Attachment:
signature.asc
Description: Digital signature