On Sat, 2013-07-27 at 19:29 -0400, Rich Mattes wrote: > and there's enough FHS issues > with default ROS packages that they all pretty much need manual > intervention before being suitable for Fedora proper. What about using Software Collections[1,2] in the mean time, until all of ROS is FHS compliant? Even after it does become compliant, we still have the issue of having multiple ROS versions available. Software collections seem to permit multiple versions of the same software, so we can have the multiple supported versions of ROS for Fedora in a third party repository. At a glance, I think ROS fits software collections really well. We can have *one* version of ROS supported in Fedora officially, say Fuerte (if we manage to pull this off, that is), and have the other versions in /opt as collections. Users can then install all versions of ROS and use what they need, the way ROS upstream supports *buntu. I haven't worked with software collections before. I just ran into a mail on the packaging SIG list and decided to check it out. BTW: I've started working on bloom for rpms. Just started hacking though. Hopefully I'll have something up in a bit. [3] [1] https://fedoraproject.org/wiki/SoftwareCollections [2] https://fedoraproject.org/wiki/Packaging:Guidelines#Software_Collection_Macros [3] https://github.com/sanjayankur31/bloom -- Thanks, Warm regards, Ankur (FranciscoD) http://fedoraproject.org/wiki/User:Ankursinha Join Fedora! Come talk to us! http://fedoraproject.org/wiki/Fedora_Join_SIG
Attachment:
signature.asc
Description: This is a digitally signed message part
_______________________________________________ robotics mailing list robotics@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/robotics
