This macro was introduced long time ago:
/usr/bin/udevadm control --reload >/dev/null 2>&1 || :
I'm not sure if packages contain udev rules should run this in scriptlet?
Meeting started by abadger1999 at 17:00:13 UTC. The full logs are
* Roll Call (abadger1999, 17:00:21)
* #142 Request for changes to FPG (abadger1999, 17:04:55)
* LINK: https://fedorahosted.org/fpc/ticket/142 (abadger1999,
* #317 Bundled Library exception request for Gazebo (abadger1999,
* LINK: https://fedorahosted.org/fpc/ticket/317 (abadger1999,
* abadger1999 to update ticket with our two ideas on how to make
gazebo-ode acceptable (abadger1999, 17:31:47)
* #389 bundled bootstrap binary exception for sbt (abadger1999,
* LINK: https://fedorahosted.org/fpc/ticket/389 (abadger1999,
* Bootstrap bundling approved for sbt bundling itself. (+1:6, 0:0,
-1:0) (abadger1999, 17:41:05)
* #338 %doc and %_pkgdocdir duplicate files and cause conflicts
* LINK: https://fedorahosted.org/fpc/ticket/338 (abadger1999,
* #339 software collections in Fedora (abadger1999, 17:50:49)
* LINK: https://fedorahosted.org/fpc/ticket/339 (abadger1999,
* LINK: http://toshio.fedorapeople.org/scls/ (abadger1999, 17:51:27)
* #387 Bundling exception: Heimdal bundles libtommath (abadger1999,
* LINK: https://fedorahosted.org/fpc/ticket/387 (abadger1999,
* Temporary exception for Heimdal to bundle libtommath until Fedora 22
granted. FPC expressed a willingness to look at granting an
extension of another two releases if this one expires without the
changes being merged upstream. We'd want to see that it was still
being worked on, just not completed. (+1:5, 0:0, -1:0)
* #340 Bundling exception for nodeunit (abadger1999, 18:38:16)
* abadger1999 to ping the ticket and ask additional question
* #358 Please make some autotools guidelines. (abadger1999,
* #382 Go Packaging Guidelines Draft (abadger1999, 18:42:57)
* LINK: https://fedorahosted.org/fpc/ticket/382 (abadger1999,
* #385 workarounds for rpm symlink <-> directory issue
* #388 recommend %autosetup over %setup (abadger1999, 18:47:41)
* LINK: https://fedorahosted.org/fpc/ticket/388 (abadger1999,
* ACTION: abadger1999 to CC panu and ask whether we need to add
buildrequires if -S VCS is used. (abadger1999, 19:01:21)
* Open floor (abadger1999, 19:02:40)
Meeting ended at 19:05:09 UTC.
* abadger1999 to CC panu and ask whether we need to add buildrequires if
-S VCS is used.
Action Items, by person
* abadger1999 to CC panu and ask whether we need to add buildrequires
if -S VCS is used.
People Present (lines said)
* abadger1999 (149)
* geppetto (62)
* Rathann (31)
* tibbs|w (28)
* RemiFedora (27)
* ktdreyer (7)
* zodbot (7)
* willb (7)
* racor (4)
* SmootherFrOgZ (3)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
-----BEGIN PGP SIGNED MESSAGE-----
As you know, most of bundled libraries provided in Icecat source
archive are already packaged in various GNU/Linux systems, but not all
can be overlooked during the compilation, some of them are libogg,
libtheora, opus or libvorbis.
Please, I need to draw your attention or advices about how to can
resolve this issue.
FPC ticket: https://fedorahosted.org/fpc/ticket/391
GPG Key: D400D6C4
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
-----END PGP SIGNATURE-----
On Thu, 2014-02-06 at 21:37 -0800, Toshio Kuratomi wrote:
> It all depends on the goals. If the goal is for an upstream to
> provide their own packages that you get from them to run on fedora
> then their method is probably fine.
Upstream doesn't provide rpms, only debs. Even the new bloom addition
only provides spec files as far as I can see, but I haven't tested it
out yet to be sure.
> If the goal is to submit to fedora then probably non-scl and
> installing to /usr is what's needed.
This is what we were working on till now. We picked ros-groovy as the
release we wanted to provide in Fedora and were packing it up with
various patches to make it install to /usr. However, at the time we made
this decision, SCLs weren't much in the picture and neither was the
Fedora.next system where we could have "rings" of application systems.
There wasn't anything else that could be done really.
> If the goal is to have parallel installed same versions then using
> scls may be the way to go. (But do note that there is a fair bit of
> overhead in terms of packaging to do this... but some portion of the
> effort carries over to future parallel versions.
Ideally, this is what we'd like to do, to be able to provide users with
all releases of ROS. For example, even at the lab I work in, some people
use ros-fuerte, some use ros-groovy (they have good support for the PR2
robot) and some have already moved on to ros-hydro. ROS upstream
intentionally choose to install packages into /opt/ so that users (most
of which are researchers) could run multiple releases in parallel.
I do understand that there's an overhead in maintaining multiple
releases. It's why we had chosen to pack up only one ROS release for
Fedora. However, with bloom generating spec files for us, this would
hopefully be manageable. If we don't have to modify upstream build files
to install to /usr, the work is *considerably* lessened too. (I'd expect
to have more people helping us too, since it's less work to package
stuff up if it's going into /opt straight away.)
Upstream recently informed me:
- With respect to the SCLs OSRF is now a registered LSB provider for
I think SCLs are the way to go. ROS fits in perfectly here.
Join Fedora! Come talk to us!
TIL that there are around a thousand packages
in Fedora that include a file named jquery.js... 
Anyway it is good to see efforts to tackle these kinds of problems
I want to ask if the packaging of grunt and jquery
blocks current package reviews of packages that bundle jquery.js?
Or can they proceed for now until jquery is actually packaged in Fedora?
ps It is going to be a long cleanup process to fix all those packages with bundled files.