Re: how to handle a common (base) package

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01/28/2011 04:59 PM, Orcan Ogetbil wrote:
> Hello all,
> During the review [1] 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.
> perl-redland
> php-redland
> python-redland
> ruby-redland
> and the above are the only common files across. The question is, where
> do these files go?

Apply common sense and add them where appropriate and where necessary ;)

> 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?
Not being familar with this package, this question confuses me.

You said "binding subpackage" - to me this implies there is a "natural 
common base 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.
Common ones can go into a common base package, those which only apply to 
individual subpackages, should go into their subpackage.

Also check if you really need to package both *.html and *.txt versions 
or if they carry identical contents.

Ralf


--
packaging mailing list
packaging@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/packaging


[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux