Greetings,
I've added a package for network scripts regarding our systemd branch
which will soon be our main branch.
For jhalfs to properly setup the Makefile for the network-script
ssection I've added this change to the CLFS/master.sh
Index: CLFS/master.sh
===================================================================
--- CLFS/master.sh (revision 3779)
+++ CLFS/master.sh (working copy)
@@ -717,6 +717,7 @@
-e 's@64@@' \
-e 's@n32@@'`
case $name in
+ network-scripts) name=clfs-network-scripts ;;
*network*) name=network-cross-lfs ;;
esac
I think that is the proper way to do it. The makefile generated the
proper commands in that section as follows:
225-network-scripts: 224-resolv
@$(call echo_message, Building)
@export BASHBIN=$(SHELL) && $(SHELL) progress_bar.sh $@ $
$PPID &
@echo "$(nl_)`date`$(nl_)" >logs/$@
@$(PRT_DU_CR) >>logs/$@
@$(call touch_timestamp)
@$(call remove_existing_dirs2,clfs-network-
scripts-20140123.tar.xz)
@$(call unpack2,clfs-network-scripts-20140123.tar.xz)
@$(call get_pkg_root2)
@source envars && \
$(crCMDSDIR)/network/$@ >>logs/$@ 2>&1 && \
$(PRT_DU_CR) >>logs/$@
@$(call remove_build_dirs2,clfs-network-scripts)
@$(call log_new_files,network-scripts)
@$(call housekeeping)
Used to, it'd be miss all of the important commands like this:
192-network-scripts: 191-resolv
@$(call echo_message, Building)
@export BASHBIN=$(SHELL) && $(SHELL) progress_bar.sh $@ $
$PPID &
@echo "$(nl_)`date`$(nl_)" >logs/$@
@$(PRT_DU_CR) >>logs/$@
@source envars && \
$(crCMDSDIR)/network/$@ >>logs/$@ 2>&1 && \
$(PRT_DU_CR) >>logs/$@
@$(call housekeeping)
Sincerely,
WIlliam Harrington
--
http://linuxfromscratch.org/mailman/listinfo/alfs-discuss
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
