> There are two issues: > 1) deploying/using pkg-conf > 2) switching from pkg-config to pkg-conf > > Switching to pkg-conf (and eliminating pkg-config) is the wrong goal > because > you will not be able to demonstrate completeness (by eliminating > pkg-config) > on any 1-2 day timeframe. >
What FreeBSD did it was just ln -s /usr/bin/pkgconf /usr/bin/pkg-conf because pkgconf is out of the box replacement to pkg-config. First deploy pkgconf, build few packages with it, then make sure that it works and rpm also handles it, and finally does pkgconfig(foobar) buildrequires works. > And again, there is very little additional gain or functionality to be had > by even 1-2 orders of magnitude faster build dependencies, or eliminating > self hosting. > > That doesn’t mean that there isn’t benefit to pkg-conf, just that there is > little > benefit to “switching”. > > 73 de Jeff > > Yes benefit is not so huge, i'd say it is compared to effort of deploying it.
_______________________________________________ OM-Cooker mailing list [email protected] http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
