From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Getting everyone started with Pakfire
Date: Wed, 16 Aug 2023 16:29:56 +0100 [thread overview]
Message-ID: <3DD4644B-D860-40AF-97AB-B18F3063C9E2@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2000 bytes --]
Hello everyone,
For our meet-up that is starting soon, I would like everyone to have a working installation of Pakfire - our new build system.
I am not sure yet in what way we are going to use it, but generally there will be an intro for everyone who hasn’t had one yet, and maybe we even get a chance to update a few packages of the distribution or something…
Because I don’t know which distributions you are using, and because we don’t have any packages for any major distribution just yet, I would like to ask everyone to install Pakfire manually on their systems in advance of our meet-up, so that we can start straight away. We should also use the time to find any issues that might occur on other distributions than Debian which is what I have been using.
Please find the source here: https://git.ipfire.org/?p=pakfire.git;a=summary
On Debian, I have to install these packages as dependencies (yes it is quite a lot):
* asciidoc, autoconf, automake, bison, build-essential, flex, intltool, libarchive-dev, libcap-dev, libcurl4-openssl-dev, libelf-dev, libgpgme-dev, libjson-c-dev, liblzma-dev, libmagic-dev, libmount-dev, libnl-3-dev, libnl-route-3-dev, libpcre2-dev, libpython3-dev, libseccomp-dev, libsolv-dev, libsqlite3-dev, libssl-dev, libsystemd-dev, libtool, libzstd-dev, pkg-config, python3-cpuinfo, python3-kerberos, python3-tornado, python3-psutil, python3-setproctitle, uuid-dev
I have no idea what the package names will be for your distribution, but I am sure you will all figure it out :)
You can use the usual three-clause build process after generating the configure script:
./autogen.sh
./configure —-prefix=/usr —-sysconfdir=/etc —-enable-debug
make
(make check)
make install
After that, you should be able to run pakfire-builder —-help.
Please let me know if that works for you up to this point and please file a bug if changes are required to make Pakfire work on your distribution.
All the best,
-Michael
next reply other threads:[~2023-08-16 15:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 15:29 Michael Tremer [this message]
2023-08-17 9:36 ` Adolf Belka
2023-08-17 9:38 ` Michael Tremer
2023-08-17 10:18 ` Adolf Belka
2023-08-17 11:20 ` Adolf Belka
2023-09-01 14:39 ` Michael Tremer
2023-09-01 16:21 ` Adolf Belka
2023-09-01 16:23 ` Michael Tremer
2023-09-01 16:37 ` Adolf Belka
2023-09-02 9:29 ` Michael Tremer
2023-09-02 10:26 ` Adolf Belka
2023-09-02 10:49 ` Adolf Belka
2023-09-02 10:53 ` Michael Tremer
2023-09-02 11:00 ` Adolf Belka
2023-09-02 11:02 ` Michael Tremer
2023-09-02 11:11 ` Adolf Belka
2023-09-02 11:33 ` Michael Tremer
2023-09-02 11:54 ` Adolf Belka
2023-09-02 16:41 ` Adolf Belka
2023-09-04 10:30 ` Michael Tremer
2023-09-04 10:29 ` Michael Tremer
2023-09-04 11:43 ` Adolf Belka
2023-09-05 16:25 ` Michael Tremer
2023-09-05 18:58 ` Adolf Belka
2023-09-05 19:02 ` Adolf Belka
2023-09-06 13:41 ` Michael Tremer
2023-09-06 17:12 ` Adolf Belka
2023-09-12 13:40 ` 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=3DD4644B-D860-40AF-97AB-B18F3063C9E2@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