On Thu, 30 May 2024 19:33:58 -0600 Luke wrote:
> On Wed, 29 May 2024 00:51:18 -0600, bill-auger wrote:
> > < #########################################################################
> > < # MODULAR CONFIGURATION
> > < #########################################################################
> > < #
> > < for file in /etc/makepkg.conf.d/*.conf; do
> > <   [[ -f "$file" ]] || continue
> > <   source "$file"
> > < done
> > < unset file
> > < BUILDDIR=/build
> > < PKGDEST=/pkgdest
> > < SRCPKGDEST=/srcpkgdest
> > < SRCDEST=/srcdest
> > < LOGDEST=/logdest  
> 
> The libre/pacman makepkg.conf no longer has the "MODULAR
> CONFIGURATION" section

we may need to restore that - mksource is broken again - not for the same
reason as before though; but because of this change (and maybe the changes to
librefetch.conf)

i may not get to this until tomorrow, so maybe luke you can look at this first
- i will report now what i discovered so far

librefetch.conf is never sourced, so the makepkg mechanism does not take-over as
expected, when the to-be-made libre source-ball is not found on the server

luke, you even left this (now legacy) comment in that file:

> This file should be 'source'd by makepkg.conf to enable librefetch

you probably should have removed it; because makepkg.conf longer does source it
- however, that assertion may actually be still correct

the deal is, when running under libremakepkg, the config files under the new
/etc/makepkg.conf.d/ get sourced from the chroot files - librefetch.conf will
not be installed in any chroot (ive actually experimented with that, and i
believe that it should never be) - librefetch.conf may literally need to be
sourced by makepkg.conf as before, or otherwise still per the hard-coded
absolute path - when i tried to do that though, libremakepkg fails to build any
package - it is probably not hard to fix; but ive not investigated further - as
soon as librefetch.conf is sourced, it throws errors and quits

  PKGDEST contains invalid characters
  SRCDEST contains invalid characters

the "invalid characters" is a newline - i think you recently refactored that
file; so maybe it is still fresh in your memory - that error may be related to
the fix for the invalid PKGDEST in /usr/bin/librefetch that was previous
breaking mksource

i will look into it more when i return, if you dont get to it first; but i think
in the end, a new libretools package will be needed to get mksource working
again
_______________________________________________
Dev mailing list
[email protected]
https://lists.parabola.nu/mailman/listinfo/dev

Reply via email to