[arch-dev-public] build automation discussions

2022-02-07 Thread Xyne via arch-dev-public
Hi, In the recent discussions about possibly adding support for x86_64-v3 the general consensus seemed to be that we need to first work on our packaging infrastructure (build pipelines, reproducible builds, etc.). Who's currently working on that and where I can get involved? Are there already any

Re: [arch-dev-public] Library dependencies

2021-12-16 Thread Xyne via arch-dev-public
On 2021-12-16 19:53 +1000 Allan McRae via arch-dev-public wrote: >Assuming that dependent library is not used elsewhere in the package, >and the extra library had a provide of its library version, then this >would add an extra dependency. > >There are several options: >1) disable autodeps - thes

Re: [arch-dev-public] Library dependencies

2021-12-15 Thread Xyne via arch-dev-public
On 2021-12-15 16:40 +1000 Allan McRae via arch-dev-public wrote: >LIB_DIRS is specified in makepkg.conf, not in PKGBUILDs. Given >usr/lib/ is not even standard for 64bit libraries, I do not want to hard >code anything. I somehow completely missed the part where you explicitly said it would be

Re: [arch-dev-public] Library dependencies

2021-12-14 Thread Xyne via arch-dev-public
On 2021-12-13 18:35 +1000 Allan McRae via arch-dev-public wrote: >Hi all, > >I submitted a patchset to pacman that I would like some packager >feed-back on. [1] > >Essentially this replaces the old libdepends/libprovides system into >something akin to that used by APK. In short, makepkg.conf wil

Re: [arch-dev-public] RFC: Rename the Trusted User role

2021-11-11 Thread Xyne via arch-dev-public
Konstantin Gizdov via arch-dev-public wrote: People are urged to choose between the following >four options: > >- Option 1: Maintainer >- Option 2: Packager   >- Option 3: Package Maintainer >- Option 4: Package & Aur Maintainer > >I realize this is a little late but I want to suggest "Repo Mainta