Query about usb_modeswitch and how to handle its packaging
-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@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Query about usb_modeswitch and how to handle its packaging
Am 20.04.2010 09:55, schrieb Huzaifa Sidhpurwala: 2. Have two srpms one for data and one for binary, with both depending on each other. This is the way to go. It also makes it easier for you to maintain it in the future. However, you must create a new review request for the data package then. Felix -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
Re: Query about usb_modeswitch and how to handle its packaging
On Tue, Apr 20, 2010 at 8:55 AM, Huzaifa Sidhpurwala huzai...@redhat.com wrote: -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. 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. Peter -- devel mailing list devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/devel
