From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: fireperf is in the Archlinux User Repository
Date: Tue, 03 May 2022 13:26:59 +0200 [thread overview]
Message-ID: <a8a98243-e3bb-6389-83ab-4d7227b3bb4a@ipfire.org> (raw)
In-Reply-To: <61A04313-18F7-4FD6-A426-707CF00DDE80@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1307 bytes --]
Hi Michael,
On 03/05/2022 11:00, Michael Tremer wrote:
> Hallo,
>
> Very nice! Thank you for your work.
Glad to have been able to help. I also found it interesting to figure out how it should be done.
>
> I like it that its only dependency is glibc.
Someone has already built it and found that there are two makedepends which are required and they did not have them installed and I obviously had them on my system and didn't notice that they were additional to the base-devel set of arch packages.
Anyway I have done an update on fireperf in the AUR to include the makedepends=('intltool' 'asciidoc') line in the PKGBUILD
>
> How do we let people know this exists?
I am not sure. Obviously there are arch users who look at new things in the AUR like the one who found my missing makedepends.
I suppose we could put the link to the AUR into the fireperf addon page in the wiki so any IPFire users who have arch linux systems will know they can go and get it.
Not sure what else.
Regards,
Adolf
>
> -Michael
>
>> On 2 May 2022, at 22:17, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>> Hi All,
>>
>>
>> fireperf has been uploaded into the AUR (Archlinux User Repository).
>>
>> https://aur.archlinux.org/packages/fireperf
>>
>>
>> Regards,
>>
>> Adolf.
>>
>
next prev parent reply other threads:[~2022-05-03 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 21:17 Adolf Belka
2022-05-03 9:00 ` Michael Tremer
2022-05-03 11:26 ` Adolf Belka [this message]
2022-05-03 11:41 ` 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=a8a98243-e3bb-6389-83ab-4d7227b3bb4a@ipfire.org \
--to=adolf.belka@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