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?
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.
Thanks, Orcan
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?
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.
Thanks, Orcan
[1] https://bugzilla.redhat.com/show_bug.cgi?id=659082
packaging mailing list packaging@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging
Put the universally common ones in a -common subpackage, and put the ones that only apply to some in those subpackages, I think.
J
On Fri, Jan 28, 2011 at 11:02 AM, Jon Ciesla wrote:
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?
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.
Thanks, Orcan
[1] https://bugzilla.redhat.com/show_bug.cgi?id=659082
packaging mailing list packaging@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging
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?
Orcan
Orcan Ogetbil wrote:
On Fri, Jan 28, 2011 at 11:02 AM, Jon Ciesla wrote:
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?
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.
Thanks, Orcan
[1] https://bugzilla.redhat.com/show_bug.cgi?id=659082
packaging mailing list packaging@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging
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?
Orcan
packaging mailing list packaging@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/packaging
Whatever license upstream says the main code is under. If that isn't clear, ask them.
J
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@lists.fedoraproject.org