Exclude paths for elfdeps dependency generator
by Till Hofmann
Hi all,
I have a question regarding the the RPM dependency generator scripts.
I'm working on packaging the ROS stack [1,2] and I'm currently dealing
with the dependency generation. My goal is to wrap all Provides and
Requires for sonames because ROS does not use proper sonames (and
therefore they shouldn't be in the ld cache), but I still want to use
the information for ROS packages. This means I want to replace:
Provides: librosconsole.so()(64bit)
=>
Provides: ros(librosconsole.so()(64bit))
[or possibly ros-kinetic(librosconsole.so()(64bit))]
and similarly for Requires.
I have a working solution [3] that wraps all ROS Provides and Requires
and generates other Provides and Requirest just as elfdeps does, but it
uses an (imho ugly) hack: As I don't want to have the normal Provides
generated by elfdeps, I have:
%__ros_path ^/usr/lib.*/ros/.*$
%__elf_exclude_path %__ros_path
in /usr/lib/rpm/fileattrs/ros.attr. I see two problems: If
%__elf_exclude_path is set by something else, it is overridden, because
I couldn't figure out how to append to the exclude path. Second,
%__elf_exclude_path should not be set at all in ros.attr, the doc [4] says:
"NAME needs to be replaced by the name choosen for the file attribute
and needs to be the same as the file name of the macro file itself"
It still works, but shouldn't according to the documentation.
So my question: Is there any other way to exclude the ROS dir to be
checked by elfdeps? I cannot just use %__requires_exclude_from because I
want my dependency generator to run on the directory.
Thanks for any hints.
Kind regards,
Till
[1] https://pagure.io/ros
[2] https://copr.fedorainfracloud.org/coprs/thofmann/ros/
[3] https://pagure.io/ros-rpm-macros
[4] http://rpm.org/user_doc/dependency_generators.html
6 years
Open Seats on the Fedora Packaging Committee
by James Antill
The Fedora Packaging Committee has some open seats and is accepting
submissions from interested candidates to serve on the FPC.
The FPC would like to thank Ralf Corsepius, Dominik 'Rathann'
Mierzejewski, and Thomas Spura for their service.
This position involves not only reviewing Packaging Guideline drafts
submitted to the FPC for consideration, but also helping rewrite drafts
to resolve issues in a more acceptable fashion. Additionally, the FPC
reviews UID/GID soft static assignment.
Currently the FPC meets on IRC weekly, on alternate
Wednesdays/Thursdays based around 12:00 EST, for approximately an
hour.
However that is likely to change back to a single day/time slot, and
the time would depend on when is good for all the members (East Coast
US and German TZs, at least).
FPC members serve for as long as they are willing, there are currently
no term limits. All decisions are voted on using a +1 (for), 0
(abstain), and -1 (against) mechanism, and all decisions must be
approved by a majority (+5). FPC Meetings do not happen if quorum (5)
is not present. Candidates who are interested should provide the
following details to the FPC for consideration, by emailing it directly
to me (james(a)fedoraproject.org).
The FPC will consider all candidates, but strongly prefers candidates
who have extensive experience packaging in Fedora. We will accept
applications for the next two weeks (deadline Wednesday, 2018-03-14).
Name:
FAS Account:
Provenpackager? (Yes/No):
Main area of packaging interest/expertise:
Reason(s) for wanting to join the FPC:
Thanks in advance,
~James
6 years