Packaging only a subset of a tool collection

[Till Maas]

Hi,

to update pam_mount I need some programs of a tool collection from the
upstream author. The tool collection[0] named hxtools contains a lot of
stuff I do not want to package. Is there any reason to only package the
two tools I need and add others whenever someone requests it?
Would someone disapprove this in a package review? Or does someone else
want to package it? ;-)

My current in-progress spec can be found here:
http://till.fedorapeople.org/tmp/hxtools.spec

Regards
Till

[0] http://jengelh.medozas.de/projects/hxtools/

[Jason L Tibbitts III]

> >>>> "TM" == Till Maas
> <opensource(a)till.name&gt; writes: 
TM> Is there any reason to only package the two tools I need and add
TM> others whenever someone requests it? Would someone disapprove this
TM> in a package review?

I don't see what would require you to package every piece of
functionality included in a upstream tarball.  Certainly you should
include sufficient comments in the spec to make the situation obvious.
Just be mindful that at some point someone else may need some of the
functionality you don't currently package, and conflicts may arise
because of this.

 - J<

[Till Maas]

On Tue, Mar 08, 2011 at 04:40:49PM -0600, Jason L Tibbitts III wrote:

>  I don't see what would require you to package every piece of
>  functionality included in a upstream tarball.  Certainly you should
>  include sufficient comments in the spec to make the situation obvious.
>  Just be mindful that at some point someone else may need some of the
>  functionality you don't currently package, and conflicts may arise
>  because of this. 
Good. Off course other programs can be included in the package once they
are required or requested by someone. For reference, the review request
I opened is located here:

https://bugzilla.redhat.com/show_bug.cgi?id=683610

Regards
Till

[Mat Booth]

On 8 March 2011 21:26, Till Maas <opensource(a)till.name&gt; wrote:
>  Hi,
>
>  to update pam_mount I need some programs of a tool collection from the
>  upstream author. The tool collection[0] named hxtools contains a lot of
>  stuff I do not want to package. Is there any reason to only package the
>  two tools I need and add others whenever someone requests it?
>  Would someone disapprove this in a package review? Or does someone else
>  want to package it? ;-)
>
>  My current in-progress spec can be found here:
>  http://till.fedorapeople.org/tmp/hxtools.spec
>
>  Regards
>  Till
>
>  [0] http://jengelh.medozas.de/projects/hxtools/
>  
We've packaged only select parts of some Eclipse plug-ins before now.
I don't see it as a problem.


-- 
Mat Booth
http://fedoraproject.org/get-fedora

[Kevin Kofler]

Till Maas wrote:
>  [0] http://jengelh.medozas.de/projects/hxtools/ 
WTF, that's a hodgepodge of many completely unrelated tools. :-(

Whoever wants to package this will also need to check the tarball for 
patent-encumbered stuff, e.g. there are tools working on MP3 files, you have 
to check whether there's any MP3 code bundled (which would have to be 
removed).

        Kevin Kofler

[Till Maas]

On Wed, Mar 09, 2011 at 01:33:18AM +0100, Kevin Kofler wrote:

>  Whoever wants to package this will also need to check the tarball for
>
>  patent-encumbered stuff, e.g. there are tools working on MP3 files, you have 
>  to check whether there's any MP3 code bundled (which would have to be 
>  removed). 
Luckily these are only perl scripts that call binaries like mpg123,
therefore afaics nothing needs to be removed from the tarball.

Regards
Till