[Dev] [PATCH] libremakepkg: fix building packages requring a rw startdir

Andreas Grapentin andreas at grapentin.org
Wed May 29 10:12:15 GMT 2019

I have to admit I don't understand the reasoning behind requiring a
read-only startdir. I like the idea of the pkgver() function being able
to modify the PKGBUILD file automagically for vcs based package sources.

Could someone explain to me why we want to break this behaviour?


On Mon, May 20, 2019 at 07:31:03PM +0200, Denis 'GNUtoo' Carikli wrote:
> On Mon, 20 May 2019 13:01:16 -0400
> bill-auger <bill-auger at peers.community> wrote:
> > only reverting that change is not enough to address the issue
> > though - we should also need to apply the patch gnutoo
> > suggested; because right now the kernels do not build
> > out-of-the-box with the standard tools - that should not be the
> > case for such a critical base package
> They now build out-of-the-box because I've added the patch to the
> libremakepkg package as we needed to get back the ability to build the
> packages that did not build anymore because of the read-only startdir.
> That way, it gives us more time to try to find the best way possible to
> fix that issue in libretools git.
> Denis.

> _______________________________________________
> Dev mailing list
> Dev at lists.parabola.nu
> https://lists.parabola.nu/mailman/listinfo/dev


my GPG Public Key:                 https://files.grapentin.org/.gpg/public.key
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20190529/5a414d1c/attachment.sig>

More information about the Dev mailing list