Query about usb_modeswitch and how to handle its packaging

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

 



-----BEGIN PGP SIGNED MESSAGE-----
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.

- --
Regards,
Huzaifa Sidhpurwala, RHCE, CCNA (IRC: huzaifas)


GnuPG Fingerprint:
3A0F DAFB 9279 02ED 273B FFE9 CC70 DCF2 DA5B DAE5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Red Hat - http://enigmail.mozdev.org/

iD8DBQFLzV31zHDc8tpb2uURAjVxAJ40ie5HVcrADk5qaSmsS6687dhWUwCgjdHO
mdulXkdmkcHt/l4emO+L0JY=
=y/O9
-----END PGP SIGNATURE-----
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux