That sounds excellent, but I don't understand exactly what it means.
I'm a systems engineer with a lot of focus on process integration.
Sometimes I tweek c programs or make helpers; not a c programmer,
but I often build with makefile to orchestrate tasks.
I see graphics/netpbm already has a patches/patch-lib_Makefile
how would you describe the high level view of libtoolize?
For example, what sort of tasks would go into preparation?
With a characterization of the problem, and objective path,
users may be able to flag packages and complete the first
phase at the same time.
excluding .o files, I see there are 106 files in
/tmp/pkg-2024Q3-670fa-Darwin_22.6.0_arm64-14.2-work/graphics/netpbm/work.aarch64/netpbm/lib/
would a first step be to preprocess them somehow?
I do not expect any doc to approach explaining the knowledge
from experience required to do the work, but some guidance
on the overall steps might make the difference of enabling
someone wanting to help, verses simply describing what is broke.
Part II. The pkgsrc developer's guide, 21.3. The configure phase
describes the use of libtool for upstream software authors.
Does that also apply to converting for libtool, pkgsrc patching
and packaging? Is there a tactical difference between patching
for pkgsrc, vs patching for upstream, when applying libtool?
thanks!
-George