tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

"special" tools e.g. yacc/lex etc. and non-NetBSD systems

Under OSes other than NetBSD lots of packages failed
because their so called base system _drammatically_ differs
from that of NetBSD. For example, lots of them fail because
they cannot find yacc, lex, uuencode and other tools used
for configuring or building.
Some of such tools are in USE_TOOLS list and many are not - doesn't

This problem is even seen under other BSDs which base systems are
close to each other.

It whould be nice to see all these packages fail under NetBSD too in
order to be visible by packagers. In this case support for operating
systems other than NetBSD (all of them!) can be drammatically improved
even if software is packaged and tested under NetBSD only.

Examples of such tools: yacc [1], lex, mkdep[2], csh [3],
compress [4], m4 [5], pkg-config [6], msgfmt [7]

I believe pkgsrc developers know how to implement this in a more
efficient way but I think wrappers for all these "bad" tools can be
packaged as special package, and then manipulation with PATH and/or
'ln -s' at 'wrapping' stage can be done.

echo 'Add yacc to USE_TOOLS first! ;-)' 1>&2
exit 1

IMHO it is absolutely useless to try to fix this kind of problem
one-by-one as soon as users send PR because they (problems) apeear
again, again and again.

Intersting (I hope) Linux statistics
Analysed package failures (direct failures): 801
failed at 'build' stage: 365 (45.5%)
failed at 'install' stage: 144 (17.9%)
         (packager's/pkgsrc bugs in most cases?)
failed at 'configure' stage: 77 (9.6%)
         (packager's/pkgsrc bugs in most cases?)

Another (harder) problem is linking against libraries from NetBSD base
system that are absent in many/most other systems.








Best regards, Aleksey Cheusov.

Home | Main Index | Thread Index | Old Index