Re: [kde-freebsd] libassuan updated

2010-06-14 Thread Alex Dupre
Doug Barton ha scritto: > Feel free to update your individual ports to libassuan 2.x at your > convenience. I'm not sure what a reasonable "time limit" on this is, but > I really don't want to keep libassuan 1.x in the tree forever. :) Well, I'd say at least until no ports will depend on it :-)

Re: [kde-freebsd] libassuan updated

2010-06-14 Thread Jun Kuriyama
2010/6/14 Doug Barton : > AFAICS you haven't responded to any of my private mail in weeks so I'm going > to take your silence as tacit approval for updating gnupg to 2.0.15 in time > to get it into 8.1-RELEASE. I don't have any reason to get them into 8.1-RELEASE, but anyway it's okay. I'll forwa

Re: [kde-freebsd] libassuan

2010-05-19 Thread Adriaan de Groot
On Wednesday 12 May 2010 06:34:37 am Doug Barton wrote: > I'm writing this message to inquire about updating ports that depend on > libassuan. It's currently at version 1.0.5, and the latest gnupg > (2.0.15) requires libassuan 2.0.0. There is an open PR that discusses > this issue, where Jason ment

Re: [kde-freebsd] libassuan

2010-05-15 Thread Max Brazhnikov
On Thu, 13 May 2010 14:59:48 -0700, Doug Barton wrote: > Meanwhile, I think we have 2 alternatives. For those ports that need > libassuan they are either updated to work with libassuan 2; or we create > a libassuan-1 port and modify those ports which must have libassuan 1 to > work with it. Version

Re: [kde-freebsd] libassuan

2010-05-13 Thread Doug Barton
Please don't strip the cc's, I want to keep everyone involved in the conversation. On 05/12/10 14:23, Max Brazhnikov wrote: > On Wed, 12 May 2010 10:42:49 -0700, Doug Barton wrote: >> On 05/12/10 07:03, Raphael Kubo da Costa wrote: >>> >>> I don't see either kdepim or kdepimlibs depending directly

Re: [kde-freebsd] libassuan

2010-05-12 Thread Max Brazhnikov
On Wed, 12 May 2010 10:42:49 -0700, Doug Barton wrote: > On 05/12/10 07:03, Raphael Kubo da Costa wrote: > > > > I don't see either kdepim or kdepimlibs depending directly on > > libassuan: kdepimlibs looks for gpgme for gpgme++, and kdepim uses > > almost the same code to look for assuan (>= 1.0.4

Re: [kde-freebsd] libassuan

2010-05-12 Thread Doug Barton
On 05/12/10 02:20, Jason E. Hale wrote: > > This transition is a little annoying, but I still think it will be much less > of a hassle to do it all together so there aren't any compatibility issues. Agreed, that's why I'm writing to try and coordinate things. :) > I maintain gpa and I could use

Re: [kde-freebsd] libassuan

2010-05-12 Thread Raphael Kubo da Costa
> Support for libassuan 2.x is in the KDE SVN and should be included in KDE 4.5 > which is due out in August. I don't see either kdepim or kdepimlibs depending directly on libassuan: kdepimlibs looks for gpgme for gpgme++, and kdepim uses almost the same code to look for assuan (>= 1.0.4) for kleo

Re: [kde-freebsd] libassuan

2010-05-12 Thread Jason E. Hale
On Wednesday 12 May 2010 00:34:37 Doug Barton wrote: > Howdy, > > I'm writing this message to inquire about updating ports that depend on > libassuan. It's currently at version 1.0.5, and the latest gnupg > (2.0.15) requires libassuan 2.0.0. There is an open PR that discusses > this issue, where J