Re: Unpackaged optional dependencies

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

 




On Jan 8, 2012, at 14:29, Spencer Jackson <spencerandrewjackson@xxxxxxxxx> wrote:

> Hi, I'm currently packaging a robotics simulator called Morse
> ( https://bugzilla.redhat.com/show_bug.cgi?id=770740 ). Morse allows its
> simulations to be interacted with via multiple middleware protocols,
> including sockets, YARP, pocolibs, ROS, and a few others. Upstream has
> recommended that I extract support for these protocols into separate
> subpackages, which seems very reasonable. Unfortunately, it doesn't seem
> that we have packages for some of these middlewares.
> 
> So, what is the best course of action? I wouldn't really object to
> writing up a few more packages for these most of these optional
> dependencies. However, packaging ROS might be... problematic
> ( http://lists.fedoraproject.org/pipermail/robotics/2011/000529.html ),
> and although an employee of their backer has indicated that he
> has some interest, I wouldn't be surprised if it took a while.
> I suppose one option would be to strip out the unsupported middleware,
> until some point in the future when there is support, then
> incrementally adding subpackages for each protocol.
> 
> Any advice would be much appreciated.
> 
> Spencer
> --
> packaging mailing list
> packaging@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/packaging

On a related note if a few other people wanted to help I would like to get ROS packaged correctly for fedora as I use it for a few different projects. 

Thanks,
Brennan Ashton
--
packaging mailing list
packaging@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/packaging



[Index of Archives]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite Forum]     [KDE Users]

  Powered by Linux