HEADS UP: Berkeley DB 4...4.7 port removals/upgrades may require manual preparation
Matthias Andree
matthias.andree at gmx.de
Mon Aug 25 10:06:24 UTC 2014
On 24. August 2014 15:36:18 MESZ, Michael Gmelin <grembo at freebsd.org> wrote:
>On Sun, 24 Aug 2014 15:08:07 +0200
>olli hauer <ohauer at gmx.de> wrote:
>
>> On 2014-08-24 14:37, Michael Gmelin wrote:
>> >
>> >
>> > On Sun, 24 Aug 2014 14:30:06 +0200
>> > Kurt Jaeger <lists at opsec.eu> wrote:
>> >
>> >> Hi!
>> >>
>> >>>> Hm, using USE_BDB=$numble looks wrong to me in devel/ice.
>> >>>>
>> >>>> Can you test the following patch.
>> >>>>
>> >>>> Index: Makefile
>> >>>>
>===================================================================
>> >>>> --- devel/ice/Makefile (revision 365910)
>> >>>> +++ devel/ice/Makefile (working copy)
>> >>>> @@ -27,7 +27,8 @@
>> >>>> .endif
>> >>>>
>> >>>> USES= iconv gmake
>> >>>> -USE_BDB= 5
>> >>>> +USE_BDB= yes
>> >>>> +WANT_BDB_VER= 5
>> >>>> INVALID_BDB_VER= 40 41 42 43 44 46 47 48 6
>> >>>> USE_LDCONFIG= yes
>> >>>> BUILD_WRKSRC?= ${WRKSRC}/cpp
>> >>
>> >>> @Kurt: Could you test and confirm? If this works, I'll commit the
>> >>> patch.
>> >>
>> >> Yes, it builds.
>> >>
>> >
>> > I created a commit request
>> >
>> > https://reviews.freebsd.org/D679
>> >
>>
>> Kurt, or you can commit this even w.o. PR.
>> The patch does not break anything but allows the port to build as
>> required. I assume there are even more easter eggs in the tree,
>> specially for USE_BDB.
>>
>
>A short grep shows that the following ports are affected, the question
>is if simply converting them to
>
>USE_BDB= yes
>WANT_BDB_VER= <prior value of USE_BDB>
>
>is the right thing to do.
>
>archivers/rpm4/Makefile
>chinese/xsim/Makefile
>comms/trustedqsl/Makefile
>comms/xastir/Makefile
>databases/dbtool/Makefile
>databases/evolution-data-server/Makefile
>databases/fortytwo-bdb/Makefile
>databases/libgda5/Makefile
>databases/memcachedb/Makefile
>databases/memcacheq/Makefile
>databases/p5-BDB/Makefile
>databases/p5-BerkeleyDB/Makefile
>databases/py-bsddb/Makefile
>databases/py-bsddb3/Makefile
>databases/rdfdb/Makefile
>devel/apr1/Makefile
>devel/libqxt/Makefile
>dns/dnshistory/Makefile
>editors/nvi-devel/Makefile
>graphics/fortytwo/Makefile
>japanese/mutt-devel/Makefile
>mail/avenger/Makefile
>mail/bogofilter/Makefile
>mail/dk-milter/Makefile
>mail/drac/Makefile
>mail/evolution-exchange/Makefile
>mail/greyfix/Makefile
>mail/isync/Makefile
>mail/meta1/Makefile
>mail/mutt/Makefile
>mail/opendkim/Makefile
>mail/spamprobe/Makefile
>net-p2p/cdonkey/Makefile
>net/freeswitch-core-devel/Makefile
>net/netatalk/Makefile
>net/netatalk3/Makefile
>net/openldap24-server/Makefile
>news/inn/Makefile
>science/gramps/Makefile
>security/pks/Makefile
>security/sks/Makefile
>sysutils/apt/Makefile
>sysutils/cfengine22/Makefile
>sysutils/cfengine32/Makefile
>www/oops/Makefile
>
>
>
>--
>Michael Gmelin
>_______________________________________________
>freebsd-ports at freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>To unsubscribe, send any mail to
>"freebsd-ports-unsubscribe at freebsd.org"
No need. USE_BDB with exact version (I.e. Without "+" should just work, if it does not, we will fix the framework.
More information about the freebsd-ports
mailing list