From mboxrd@z Thu Jan  1 00:00:00 1970
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Getting everyone started with Pakfire
Date: Thu, 17 Aug 2023 11:36:29 +0200
Message-ID: <5bac4727-e5b2-453b-916e-21778aeff7f4@ipfire.org>
In-Reply-To: <3DD4644B-D860-40AF-97AB-B18F3063C9E2@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5679986371653874493=="
List-Id: <development.lists.ipfire.org>

--===============5679986371653874493==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

I am using Arch Linux.

I already do some building of my bacula client package on my laptop so=20
it has the normal build tools installed.

To get autogen.sh to run I had to install intltool

To get configure to run I had to additionally install.

asciidoc, python-py-cpuinfo, python-pykerberos, python-systemd,=20
python-tornado and libsolv

After that configure ran without any problems, as did make.

Although make check is in brackets I gave it a go but got 1 pass and 26=20
fails. The only pass was for test.py
I ran the make check a second time and then two passed - test.py and=20
progressbar.py
Further running of make check didn't change anything.

make install went fine and after that I can run pakfire-builder --help=20
and get the help screen.

Regards,
Adolf.


On 16/08/2023 17:29, Michael Tremer wrote:
> Hello everyone,
>
> For our meet-up that is starting soon, I would like everyone to have a work=
ing installation of Pakfire - our new build system.
>
> I am not sure yet in what way we are going to use it, but generally there w=
ill be an intro for everyone who hasn=E2=80=99t had one yet, and maybe we eve=
n get a chance to update a few packages of the distribution or something=E2=
=80=A6
>
> Because I don=E2=80=99t know which distributions you are using, and because=
 we don=E2=80=99t have any packages for any major distribution just yet, I wo=
uld like to ask everyone to install Pakfire manually on their systems in adva=
nce of our meet-up, so that we can start straight away. We should also use th=
e 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=3Dpakfire.git;a=3Dsu=
mmary
>
> On Debian, I have to install these packages as dependencies (yes it is quit=
e a lot):
>
> * asciidoc, autoconf, automake, bison, build-essential, flex, intltool, lib=
archive-dev, libcap-dev, libcurl4-openssl-dev, libelf-dev, libgpgme-dev, libj=
son-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-cp=
uinfo, python3-kerberos, python3-tornado, python3-psutil, python3-setproctitl=
e, 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 confi=
gure script:
>
>    ./autogen.sh
>    ./configure =E2=80=94-prefix=3D/usr =E2=80=94-sysconfdir=3D/etc =E2=80=
=94-enable-debug
>    make
>    (make check)
>    make install
>
> After that, you should be able to run pakfire-builder =E2=80=94-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

--=20
Sent from my laptop


--===============5679986371653874493==--