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?

If it is a Fedora package, then it should integrate into the system directories. If it is a third-party package that doesn't follow Fedora's packaging standards, then this is what /opt is for. "ros" is registered as a provider name for the Open Source Robotics Foundation (http://www.lanana.org/lsbreg/providers/providers.txt), so if that's the ROS we're talking about, then /opt/ros is right.

That doesn't answer the question about SCLs though.

Hi, On Fri, 2014-02-07 at 19:49 +0100, Björn Persson wrote: > If it is a Fedora package, then it should integrate into the system > directories. If it is a third-party package that doesn't follow > Fedora's packaging standards, then this is what /opt is for. "ros" is > registered as a provider name for the Open Source Robotics Foundation > (http://www.lanana.org/lsbreg/providers/providers.txt), so if that's > the ROS we're talking about, then /opt/ros is right. Yes. That's the ROS we're talking about. > > That doesn't answer the question about SCLs though. So, in the future, are SCLs going to be "Fedora packages" that we serve from our repos via koji/bodhi? Or, are we going to continue serving them off copr and other places? From all the talk about Fedora.next and the rings and the SCL guidelines etc., I *thought* we'd include SCLs in the Fedora repos. I talked this over with the robotics SIG and the SCL mailing list. Even though just placing files in /opt/ros/{release} seems OK, SCLs are a much cleaner way to go. I'm pushing stuff to a copr repo for the time being.