Mmm true...<br><br>With this package system you can build the package from source or install an already built binary package (if you dont want to tune compile options). In both cases there is a package database that is updated...
<br><br>So the best way to do the check might be using the database with pkg_info -e <pkg_name> -L<br>and check the files listed for this package are actually present.<br><a href="http://man.netbsd.se/?find=pkg_info+1+20">
http://man.netbsd.se/?find=pkg_info+1+20</a><br>Not sure how this can fit in the CMake package detection system ...<br><br>However pkgsrc has been ported to many unix platforms including linux and I dont know how it works exactly on those platforms (never tried), but I guess the raw commands like pkg_info might be the same...
<br><br>FYI, cmake is itself a package in pkgsrc (version 2.0 now...)<br><a href="ftp://ftp.netbsd.org/pub/NetBSD/packages/pkgsrc/devel/cmake/README.html">ftp://ftp.netbsd.org/pub/NetBSD/packages/pkgsrc/devel/cmake/README.html
</a><br><br>So you might consider contacting the pkgsrc guys to be sure... they will now the best way to do it :-)<br><p>
The following mailing lists may be of interest to pkgsrc users:
</p>
<div class="itemizedlist"><ul type="disc"><li>
<a href="http://www.netbsd.org/MailingLists/index.html#pkgsrc-bugs" target="_top">pkgsrc-bugs</a> --
a list where problem reports related to pkgsrc are sent and
discussed</li><li>
<a href="http://www.netbsd.org/MailingLists/index.html#pkgsrc-bulk" target="_top">pkgsrc-bulk</a> --
a list where the results of pkgsrc bulk builds are sent and
discussed</li><li>
<a href="http://www.netbsd.org/MailingLists/index.html#pkgsrc-changes" target="_top">pkgsrc-changes</a>
--
a list where all commit messages to pkgsrc are sent</li><li>
<a href="http://www.netbsd.org/MailingLists/index.html#tech-pkg" target="_top">tech-pkg</a> --
a general discussion list for all things related to pkgsrc</li></ul></div><br>It would be really nice for Cmake to be able to shipout with up-to-date and widely tested package detection scripts :-) Many tests needed tho...
<br>The pkgsrc system is frozen every quarter of the year to test them all as much as possible.<br>To have a generic detection scheme depending on the package system would be awesome :-)<br><br>Not sure how it works now on different package systems, and how this can be achieved...
<br><br>Anyway dont hesitate to let me know if I can be of any help ;-)<br><br>Thanks a lot for that !<br><br><br><br><br><br><br><br><div><span class="gmail_quote">2005/12/30, Brad King <<a href="mailto:brad.king@kitware.com">
brad.king@kitware.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Asmodehn Shade wrote:<br>> I would like the detection scripts to detect the packaged installed by
<br>> pkgsrc (<a href="http://www.pkgsrc.org">www.pkgsrc.org</a> <<a href="http://www.pkgsrc.org">http://www.pkgsrc.org</a>>)<br>><br>> pkgsrc is a portable package management system, and by default it<br>> install all the packages under /usr/pkg (on my NetBSD at least...) like
<br>> linux pkg systems installs on /usr/local...<br><br>Do packages installed by this system have any kind of manifest? It<br>would be easier to detect packages by loading files that describe them<br>instead of searching for separate pieces.
<br><br>-Brad<br></blockquote></div><br>