From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Building packages for IPFire 3.x
Date: Mon, 26 Nov 2018 13:48:33 +0000 [thread overview]
Message-ID: <1bc13eca5e5042313a50cb61aaa6eb12b5f19d59.camel@ipfire.org> (raw)
In-Reply-To: <daff817d-dda3-94c4-6cf8-639c3979edec@link38.eu>
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]
Hi,
On Sun, 2018-11-25 at 20:56 +0100, Peter Müller wrote:
> Hello *,
>
> sorry for being so quiet during the last weeks.
yes, I was already getting worried and gave you a call :)
> Updating packages and provide some system hardening (kernel, SSH, et al.)
> for IPFire 3.x is on my todo list for a long time now. While searching for
> further information about how to build packages for this distribution,
> I came across https://wiki.ipfire.org/devel/build_package/start .
Yes, that's correct.
> As far as I understood, an instance of IPFire 3.x is needed to build
> packages on it; there is no other way documented. Is this correct? What
> happened to https://pakfire.ipfire.org/ ?
The webUI is currently offline. I am quite busy with the rest of the
infrastructure, but when that is done, this will be next.
You can build packages without this, but you cannot do any scratch builds.
> Further, the *.nm files seem to be somewhat tricky. A quick lookup in the
> wiki did not show up any noob documentation. In case the is one available
> (man page, etc.), how do I find it?
Have you seen this?
https://wiki.ipfire.org/devel/pakfire/start
Are there any questions you have that are not answered there?
Best,
-Michael
>
> Thanks, and best regards,
> Peter Müller
next prev parent reply other threads:[~2018-11-26 13:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-25 19:56 Peter Müller
2018-11-26 13:48 ` Michael Tremer [this message]
2018-11-26 17:16 ` Peter Müller
2018-11-27 10:13 ` 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=1bc13eca5e5042313a50cb61aaa6eb12b5f19d59.camel@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