Query about usb_modeswitch and how to handle its packaging

Peter Robinson pbrobinson at gmail.com
Tue Apr 20 08:16:46 UTC 2010

On Tue, Apr 20, 2010 at 8:55 AM, Huzaifa Sidhpurwala
<huzaifas at redhat.com> wrote:
> Hash: SHA1
> Hi All,
> I maintain usb-modeswitch in fedora. Recently upstream divided the main
> tar ball into two parts, the code which builds into the usb_modeswitch
> binary and the data part which contains the udev rules.
> Initially there was just one tar ball with both, and my spec builds two
> rpms out of that namely usb_modeswitch and usb_modeswitch-data.
> Now upstream says that his intention of making two tar balls was to
> enable updating the data part more frequently then the code, which makes
> sense.
> Now i have two options:
> 1. Have just one srpm, which builds from the two tar balls, if that is
> done, the upstream purpose of updating the data more frequently is lost.
> Also upstream says usb_modeswitch has to depend on usb_modeswitch-data
> and vice versa.
> 2. Have two srpms one for data and one for binary, with both depending
> on each other.
> Which one do you think is the best option.
> Thanks in advance.

2 is definitely the best option as it allows to push updates to the
data package without the binary component.

You might want to look at how hal and hal-info does the deps cross check.


More information about the devel mailing list