Re: mixing different upstream sources in one package
sean finney <email@example.com> wrote:
> hi jay,
> On Sat, Nov 19, 2005 at 12:27:33PM -0500, Jay Berkenbilt wrote:
>> I'm not sure that, as an upstream author, I would necessarily want
>> the debian version of my package to be bundled with other software
>> that was similar in functionality but otherwise unrelated to my
> as an upstream author, you'd better be allright with it if you've
> released your software under a free-as-in-speech license. that's kind
> of the point of Free Software. of course, it goes without saying
> that any terms of the original work's copyright need to continue
> to be honored (as you mentioned there can't be any licensing
> conflicts). for most gpl-within-gpl situations, this simply means
> updating debian/copyright.
David Moreno Garza <firstname.lastname@example.org> wrote:
> On 12:27 Sat 19 Nov 2005, Jay Berkenbilt wrote:
>> little. I'm not sure that, as an upstream author, I would necessarily
>> want the debian version of my package to be bundled with other
>> software that was similar in functionality but otherwise unrelated to
>> my package.
> I don't agree with this, then upstream author should maintain the
> package and decide what's the best action to be taken for the
> package itself.
Point taken on both counts; I retract my statement and offer this
As an upstream author, I would accept contributions and incorporate
them into the package. (I have done this before.) As an upstream
author who was not the packager, I would offer my opinions to the
packager but would defer to the packager's judgment or preference.
I think my objections would be completely mitigated by simply
mentioning this in the package description.
Luk Claes <email@example.com> wrote:
> Maybe you could consider to add a package psutils-addons or
> something similar?
Yes, this would be a definite possibility -- it would allow the
convenience of bundling everything in one source package without the
issue of having the binary package whose name matches upstream pull in
additional software. In this case, it may not be worth the trouble,
but it's a good suggestion to keep in mind.
Jay Berkenbilt <firstname.lastname@example.org>