From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: libloc 0.9.16 rootfile changes
Date: Mon, 21 Nov 2022 13:57:07 +0000 [thread overview]
Message-ID: <0fcd2e8e-7264-79ef-e247-8cabf96d5ce4@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1845 bytes --]
Hello *,
while trying to update libloc in IPFire 2.x, I noticed a possible quirk in the way the
Perl module and man page files are currently installed. The rootfile diff looks as follows:
diff --git a/config/rootfiles/common/libloc b/config/rootfiles/common/libloc
index 7eb94217e..628ac343f 100644
--- a/config/rootfiles/common/libloc
+++ b/config/rootfiles/common/libloc
@@ -1,3 +1,8 @@
+#Location.3
+Location.pm
+#auto
+#auto/Location
+auto/Location/Location.so
#etc/cron.daily
#etc/cron.daily/location-update
usr/bin/location
@@ -22,10 +27,6 @@ usr/bin/location
#usr/lib/libloc.so
usr/lib/libloc.so.1
usr/lib/libloc.so.1.0.2
-usr/lib/perl5/site_perl/5.36.0/xxxMACHINExxx-linux-thread-multi/Location.pm
-#usr/lib/perl5/site_perl/5.36.0/xxxMACHINExxx-linux-thread-multi/auto/Location
-#usr/lib/perl5/site_perl/5.36.0/xxxMACHINExxx-linux-thread-multi/auto/Location/.packlist
-usr/lib/perl5/site_perl/5.36.0/xxxMACHINExxx-linux-thread-multi/auto/Location/Location.so
#usr/lib/pkgconfig/libloc.pc
#usr/lib/python3.10/site-packages/_location.la
usr/lib/python3.10/site-packages/_location.so
@@ -38,7 +39,6 @@ usr/lib/python3.10/site-packages/location/i18n.py
#usr/lib/python3.10/site-packages/location/importer.py
usr/lib/python3.10/site-packages/location/logger.py
#usr/share/locale/de/LC_MESSAGES/libloc.mo
-#usr/share/man/man3/Location.3
#var/lib/location
var/lib/location/database.db
var/lib/location/ipset
It appears that, despite ./configure called with parameters such as "--disable-man-pages",
libloc always installs a man page, and now places Perl files in the current working directory
rather than something like /usr/lib/perl5/site_perl/5.36.0/...
Does the ./configure call need additional parameters? Is this behaviour intended?
Thanks, and best regards,
Peter Müller
next reply other threads:[~2022-11-21 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 13:57 Peter Müller [this message]
2022-11-21 14:23 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0fcd2e8e-7264-79ef-e247-8cabf96d5ce4@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox