On 2011-05-25 02:32, Philip M. Gollucci wrote: > On 5/24/2011 4:59 PM, Olli Hauer wrote: >> Unfortunately the package name for apr reflects the build options >> and we can end up with a view hundred different package names. >> (5 options * possible (bdb|mysql|pgsql|ldap|sqlite) versions) > Thats not quite true, I thought I stripped most of this before. If not > I think we should go head and do so it seems to be more trouble then its > worth.
A test with "make -V PKGNAME" machine 1 apr-ipv6-devrandom-gdbm-db42-1.4.5.1.3.12 with all options apr-ipv6-devrandom-gdbm-db42-ldap24-mysql55-pgsql84-sqlite3-1.4.5.1.3.12 machine 2 apr-nothr-devrandom-1.4.5.1.3.12 apr-ipv6-devrandom-gdbm-db47-1.4.5.1.3.12 with all options apr-ipv6-devrandom-gdbm-db47-ndbm-ldap24-mysql55-pgsql90-sqlite3-1.4.5.1.3.12 It has also a good site. During testbuilds I've logged everything to $PKGNAME.log, so I was able to see easily what was tested. Anyway, it's not clear to me why I had no issues to build the the database wit packaudit on 7.4 but not on a identical 8.2 machine ... >> >> >> So what's the best way to document the apr issue? >> >> This entry is not recognized by portaudit and vxquery. >> <package> >> <name>apr1</name> >> <range><lt>1.4.5.1.3.12</lt></range> >> </package> > > _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscr...@freebsd.org"
