how to handle a common (base) package
Orcan Ogetbil wrote:
> On Fri, Jan 28, 2011 at 11:02 AM, Jon Ciesla wrote:
>> Orcan Ogetbil wrote:
>>> Hello all,
>>> During the review  of the redland-bindings package , I came across
>>> a situation where there are common %doc files that need to be shared
>>> across different bindings. These are:
>>> %doc AUTHORS COPYING COPYING.LIB ChangeLog
>>> %doc LICENSE.txt NEWS README TODO
>>> %doc LICENSE.html NEWS.html README.html TODO.html
>>> %doc LICENSE-2.0.txt NOTICE
>>> %doc RELEASE.html
>>> The package has perl, php, python and ruby bindings, each of which has
>>> its own subpackage, i.e.
>>> and the above are the only common files across. The question is, where
>>> do these files go?
>>> Shall we make a common package and make all the binding subpackages
>>> depend on it? If so, what shall be the name of the common package? I
>>> need to add that some of the bindings have different licenses, so some
>>> of the above license files may be irrelevant for some of the bindings.
>>>  https://bugzilla.redhat.com/show_bug.cgi?id=659082
>>> packaging mailing list
>> Put the universally common ones in a -common subpackage, and put the
>> ones that only apply to some in those subpackages, I think.
> Okay, then what will be the license of the -common subpackage?
> packaging mailing list
Whatever license upstream says the main code is under. If that isn't
clear, ask them.
in your fear, seek only peace
in your fear, seek only love
packaging mailing list