Hi,
Bloom, the ROS generator system has recently gotten support to generate rpms[1]. At the moment, the author is simply putting releases into /opt/ros/$ros-release and isn't making use of SCLs. Is this OK, or should they use SCLs?
As you'll see from the ticket, I've already pointed him to SCLs, but considering that he's already using /opt/ros/$ros-release, and not the system directories, I'm wondering how using SCLs would be any different?
[1] https://github.com/ros-infrastructure/bloom/pull/228
PS: I've also sent this to the fedora-packaging-SIG mailing list. I wasn't too sure what the best list for this question is.
On 02/07/2014 01:54 AM, Ankur Sinha wrote:
Hi,
Bloom, the ROS generator system has recently gotten support to generate rpms[1]. At the moment, the author is simply putting releases into /opt/ros/$ros-release and isn't making use of SCLs. Is this OK, or should they use SCLs?
As you'll see from the ticket, I've already pointed him to SCLs, but considering that he's already using /opt/ros/$ros-release, and not the system directories, I'm wondering how using SCLs would be any different?
[1] https://github.com/ros-infrastructure/bloom/pull/228
PS: I've also sent this to the fedora-packaging-SIG mailing list. I wasn't too sure what the best list for this question is.
softwarecollections mailing list softwarecollections@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/softwarecollections
No problem in using regular packaging for /opt. Many people already do so. SCLs are better if you have two packages of different version on one system, because installation in different directory don't solve rpm conflicts.
Marcela
softwarecollections@lists.fedorahosted.org
-
Ankur Sinha -
Marcela Mašláňová