#6024: fontforge-20141230
-------------------------+--------------------------
Reporter: fo | Owner: blfs-book@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.7
Component: BOOK | Version: SVN
Severity: normal | Resolution:
Keywords: |
-------------------------+--------------------------
Comment (by fo):
Have you tried to build with it?
It needs an active connection and git, the same way as
[https://github.com/fontforge/fontforge/archive/20141230.tar.gz]
Think this is not acceptable in BLFS, as required, only as optional, but
personally I would accept it.
Another option would be if we get it ourselves ''gnulib'' (see below
bootstrap requiring git for gnulib) and include in the tarball. I have
done this for some package that I don't remember before.
I have created a new package running inside the source directory you
provided:
{{{
git init
git clone --depth 365 'git://git.sv.gnu.org/gnulib' 'gnulib'
git submodule init
git submodule update
cp -va bootstrap.conf bootstrap.conf.conf
cat >> bootstrap.conf << "EOF"
# Remove unnecessary warnings
func_gnulib_tool () { :; }
EOF
}}}
This can use book's instructions, just adding the switch --skip-git to
bootstrap. It builds, installs and runs fine.
The modification of the ''bootstrap.conf'' file is needed just to remove
the warnings:
{{{
bootstrap: warning: No 'git' found; imported gnulib modules may be
outdated.
bootstrap: warning: No 'gnulib-tool' found; gnulib modules may be missing.
}}}
The copy of the original ''bootstrap.conf'' is just for documentation
sake.
Is a tarball based on that acceptable for the book? (This question is
extended to everybody) We could then rename to the convention in use now
in the book for version. It will be a little hard to explain how the
tarball was obtained, in the package page.
BTW, I was wrong yesterday, it is executed by ''botstrap''.
However, if I compress 20141230.tar.gz as xz, your tarball is smaller by
about 5 MB. Considering that the gz compressed tarball is 24 MB and yours
xz compressed is 13 MB if you later remove from your directory, when it is
copied into the public directories, it is better for anduin.
About git (edited, breaking the lines and removed avery long one having
only ''lcdigits.png'':
{{{
$ xzgrep git fontforge-2.0.20141230-simulation-2015.01.12-12h56m54s.log.xz
WARNING: you do not have a .git directory in your build, so one is being \
created
Initialized empty Git repository in \
/home/fernando/tmp/porg-
build-2015.01.12-12h56m54s/fontforge-2.0.20141230/.git/
bootstrap: running: git clone --depth 365 \
'git://git.sv.gnu.org/gnulib' 'gnulib'
bootstrap: running: git submodule init
bootstrap: running: git submodule update
Updating ./m4/.gitignore (backup in ./m4/.gitignore~)
libspiro check no
https://github.com/fontforge/libspiro
libuninameslist check no \
https://github.com/fontforge/libuninameslist
}}}
I have a physician appointment this afternoon, so perhaps I will only come
back to BLFS tomorrow.
But thank you all for the replis of a mail, and tomorrow I will try to
reply more deeply.
--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/6024#comment:17>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
