Re: Getting BLFS builder to recognize empty files

"Pierre Labastie" ([email protected] via alfs-discuss Mailing List) <[email protected]> Wed, 5 Mar 2025 14:20:50 +0100
Newsgroups gmane.linux.lfs.automated
Message-ID <[email protected]>
On 3/5/25 09:01, "Cliff McDiarmid" ([email protected] via 
alfs-discuss Mailing List) wrote:
> Hi
>
> I'm finding the 'Blfs builder' very good after practice.  One thing though.
> Why are some empty package files in the tracking directory, /var/lib/jhalfs/
> BLFS, pulled in on a next run, and some which have the right label are not?
> Any ideas here?

No idea why ATM. Normally, those files are integrated into instpkg.xml 
at the beginning of "make", and immediately removed.

> I've got three in there with the correct package version and
> numbers which won't move.  I thought it might be linked the capital letters
> but it's not.

It may be a permission problem. The empty file is removed with "rm -f". 
So if the user running make does not have the right to remove the file, 
because the user cannot write either to the file or to the directory for 
example, then it fails silently.

Note that it would be interesting to see whether the integration into 
instpkg.xml has been done.

Pierre

-- 
http://lists.linuxfromscratch.org/sympa/info/alfs-discuss
Unsubscribe: See the above information page