On 5/1/19 10:53 AM, Pierre Labastie via blfs-dev wrote:
Hi,
The "Command Explanation" about run-parts on the libpaper page is:
"""
paperconfig is a script which will invoke run-parts if /etc/libpaper.d exists.
No other BLFS package installs this, so we create it here.
"""
But actually, run-parts is also installed by fcron.
So, the sentence above is wrong. We could make a separate page for run-parts,
and have both fcron and libpaper depend on it (run-time). That would be the
cleanest way.
We could recommend fcron for libpaper, and keep run-parts only in fcron. But
libpaper itself does not use the fcron facilities.
We could stay this way, but make an xinclude for run-parts (so that we are
sure that both versions are the same), and of course remove "No other BLFS
package installs this ...". Might be the easiest to maintain.
Thoughts?
Pierre
I think we should separate run-parts into a separate page/package (maybe
after Bash Startup Configuration Files?) and then reference it in both
libpaper and fcron.
My main reasoning behind this is that it would remain consistent with
things like the remove-la-files.sh script - something that we recommend
that the user create after LFS.
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
