#2941: libpipeline documentation wrongly claims that it does not have a test
suite
----------------------+-----------------------------------------------------
Reporter: cjwatson | Owner: bdubbs@…
Type: defect | Status: assigned
Priority: normal | Milestone: 7.0
Component: Book | Version: SVN
Severity: normal | Keywords:
----------------------+-----------------------------------------------------
Comment(by bdubbs@…):
Replying to [comment:6 cjwatson]:
> Bruce, I can't speak for check's test suite errors, but perhaps you
should report them as a bug to its maintainers if it isn't discussed in
its documentation.
I checked the source and the 'errors' appear to be intentional and are not
classified as failures.
> pkg-config is a widespread dependency nowadays, and it's small and of
general utility. I realise LFS is pretty minimalist, but I honestly think
you'd be much better off using pkg-config rather than advising your users
to fiddle about with LDFLAGS or other similar hacks (as I see you advise
for man-db's use of libpipeline); that's a distinctly error-prone process
and doesn't seem to have much educational value either. The point of pkg-
config is that other packages and users shouldn't need to keep track of
the specifics of how libraries need to be compiled and linked against.
The problem with pkg-config is that it has proliferated dependencies. It
uses glib which now in turn requires PCRE and python. There are only two
packages in the base LFS system that use pkg-config: E2fsprogs and man-db;
and they have relatively simple work arounds.
I do think that pkg-config should be built early in the BLFS process of
fleshing out a system, but it can be delayed until needed there.
--
Ticket URL: <http://wiki.linuxfromscratch.org/lfs/ticket/2941#comment:8>
LFS Trac <http://wiki.linuxfromscratch.org/lfs/>
Linux From Scratch: Your Distro, Your Rules.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-book
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page