Fernando de Oliveira wrote:
On 30-12-2014 20:25, Bruce Dubbs wrote:
Ken Moffat wrote:
Bootscripts are always a pain - AFAIK, there is no way to generate
the new dated tarball "by hand" : it gets generated when the book
is rendered iff there is a new version in general.ent. You have
done that and added the uninstall target.
I'm not sure I understood.
make bootscripts
Would this make a tarball just for my local use?
Yes. Take a look at the Makefile. If you make changes that you don't
want to commit, then they are local.
bootscripts:
@VERSION=`grep "bootscripts-version " general.ent | cut -d\" -f2`; \
BOOTSCRIPTS="blfs-bootscripts-$$VERSION"; \
if [ ! -e $$BOOTSCRIPTS.tar.xz ]; then \
rm -rf $(RENDERTMP)/$$BOOTSCRIPTS; \
mkdir $(RENDERTMP)/$$BOOTSCRIPTS; \
cp -a ../bootscripts/* $(RENDERTMP)/$$BOOTSCRIPTS; \
rm -rf ../bootscripts/archive; \
tar -cJhf $$BOOTSCRIPTS.tar.xz -C $(RENDERTMP) $$BOOTSCRIPTS; \
fi
should do what you want. If you want to regenerate without changing the
date in general.ent, just delete or rename the current tarball in the
top level of the sources where the Makefile is located.
I can't find that tarball.
For me:
$ cd ~/BLFS/trunk/BOOK
$ rm -fv blfs-bootscripts*
removed 'blfs-bootscripts-20141226.tar.xz'
$ make bootscripts
I then have ~/BLFS/trunk/BOOK/blfs-bootscripts-20141226.tar.xz
You do need to have retrieved BLFS/trunk from svn so you have
~/BLFS/trunk/bootscripts
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
