From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Question regarding update of util-macros
Date: Thu, 24 Jun 2021 12:24:55 +0100 [thread overview]
Message-ID: <D4898367-2A12-429C-9401-066412748A8C@ipfire.org> (raw)
In-Reply-To: <dd163e3d-cb17-2a09-2175-941807b99282@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1735 bytes --]
Hello,
> On 22 Jun 2021, at 17:38, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi Michael,
>
> On 22/06/2021 14:24, Michael Tremer wrote:
>> Hello,
>> I do not know what would require this.
>> You can try commenting it out in make.sh and see if the build runs through. If anything, it should be a build time dependency.
> Good idea. I tried that and there was no problem with the build.
>
> Searching in IPFire git I found that util-macros was originally introduced as a build dependency for pciaccess which was a dependency of libvirt.
>
> Looks like the updates of pciaccess have removed the util-macros build dependency, although I could not find any mention in the Changelog of pciaccess.
>
> I would propose a patch to remove this from IPFire. Let me know if you agree and I will submit a patch.
It looks like they dropped that dependency when they changed from autotools to meson.
-Michael
>
> Regards,
> Adolf.
>> Best,
>> -Michael
>>> On 21 Jun 2021, at 13:57, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>
>>> Hi everyone,
>>>
>>> I noted that util-macros is from 2014 and a version from 2021 is available.
>>>
>>> So I was going to update it but realised that it is a package related to Xorg, which as far as I am aware is not used on IPFire. util-macros is an addon but the rootfile is in the common section of the folder structure and has all the files commented out, so it looks like it is installed to enable other packages to be installed that expect it to be present.
>>>
>>>
>>> I just wanted to check that this package is actually still required to be in IPFire before I spend time trying to update it.
>>>
>>>
>>> Regards,
>>>
>>> Adolf.
>>>
prev parent reply other threads:[~2021-06-24 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 12:57 Adolf Belka
2021-06-22 12:24 ` Michael Tremer
2021-06-22 16:38 ` Adolf Belka
2021-06-24 11:24 ` Michael Tremer [this message]
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=D4898367-2A12-429C-9401-066412748A8C@ipfire.org \
--to=michael.tremer@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