On 2017/07/10 19:49, Rafael Sadowski wrote:
> > Personally I'd probably merge it all into security/qca and name
> > it as qca-2.x.x, just get rid of qca2, then the only quirks entry
> > would be one obsolete entry for qca-tls ...
>
> The idea is good and works for me:
>
> # -> pkg_info | grep
On Mon Jul 10, 2017 at 09:04:56AM +0100, Stuart Henderson wrote:
> On 2017/07/09 23:24, Rafael Sadowski wrote:
> > On Sun Jul 09, 2017 at 10:40:14PM +0200, Landry Breuil wrote:
> > > On Sun, Jul 09, 2017 at 10:22:51PM +0200, Rafael Sadowski wrote:
> > >
> > > > > > +@conflict qca-1*
> > > > > >
On 2017/07/09 23:24, Rafael Sadowski wrote:
> On Sun Jul 09, 2017 at 10:40:14PM +0200, Landry Breuil wrote:
> > On Sun, Jul 09, 2017 at 10:22:51PM +0200, Rafael Sadowski wrote:
> >
> > > > > +@conflict qca-1*
> > > > > +@pkgpath security/qca
> > > >
> > > > I suppose you've tested the upgrade
On Sun, Jul 09, 2017 at 11:24:38PM +0200, Rafael Sadowski wrote:
> On Sun Jul 09, 2017 at 10:40:14PM +0200, Landry Breuil wrote:
> > On Sun, Jul 09, 2017 at 10:22:51PM +0200, Rafael Sadowski wrote:
> >
> > > > > +@conflict qca-1*
> > > > > +@pkgpath security/qca
> > > >
> > > > I suppose you've
On Sun Jul 09, 2017 at 10:40:14PM +0200, Landry Breuil wrote:
> On Sun, Jul 09, 2017 at 10:22:51PM +0200, Rafael Sadowski wrote:
>
> > > > +@conflict qca-1*
> > > > +@pkgpath security/qca
> > >
> > > I suppose you've tested the upgrade path :)
> >
> > This was the last task after final diff and
On Sun, Jul 09, 2017 at 10:22:51PM +0200, Rafael Sadowski wrote:
> > > +@conflict qca-1*
> > > +@pkgpath security/qca
> >
> > I suppose you've tested the upgrade path :)
>
> This was the last task after final diff and it works with the main port:
>
> "qca2-2.0.3p2->2.1.3: ok"
>
> but not with
On Sun Jul 09, 2017 at 11:02:38AM +0200, Landry Breuil wrote:
> On Sun, Jul 09, 2017 at 10:30:06AM +0200, Rafael Sadowski wrote:
>
> So, i've read through it, comments inline.
>
> > - security/qca-ossl \
> > + security/qca2,,-ossl \
>
> Why the double comma ? i think
nflicts with
> > > security/qca (qca1) and upcoming qca2-qt5. The QcaConfig extension was
> > > necessary to patch and modify less the consumers.
> > >
> > > But after your e-mail I grep for security/qca and there are no consumers.
> > > New idea
; a good idea. I renamed share lib and pkgname to avoid conflicts with
> > security/qca (qca1) and upcoming qca2-qt5. The QcaConfig extension was
> > necessary to patch and modify less the consumers.
> >
> > But after your e-mail I grep for security/qca and there are no consum
e consumers.
>
> But after your e-mail I grep for security/qca and there are no consumers.
> New idea because we can get rid of qca1:
>
> - remove the old security/qca.
> - update qca from 2.0.3 to 2.1.3. (with MULTI_PACKAGES to remove
> security/{qca-ossl,qca-gnupg}
You me
On Fri Jul 07, 2017 at 10:03:56PM +0200, Landry Breuil wrote:
> On Fri, Jul 07, 2017 at 09:14:01PM +0200, Rafael Sadowski wrote:
> > Hi All,
> >
> > after a long journey with all qca2 consumers, I'm happy to publish this
> > diff. First of all the security/qca2 changelog part:
> >
> > - Update
On Fri, Jul 07, 2017 at 09:14:01PM +0200, Rafael Sadowski wrote:
> Hi All,
>
> after a long journey with all qca2 consumers, I'm happy to publish this
> diff. First of all the security/qca2 changelog part:
>
> - Update from 2.0.3 to 2.1.3.
> - Transform security/{qca-ossl,qca-gnupg} in one
Hi All,
after a long journey with all qca2 consumers, I'm happy to publish this
diff. First of all the security/qca2 changelog part:
- Update from 2.0.3 to 2.1.3.
- Transform security/{qca-ossl,qca-gnupg} in one security/qca2 port with
MULTI_PACKAGES -ossl and -gnupg.
- rRename PKGNAME from
I was wondering if there's anyone who has run into this:
One thing I've run into the very few times I tried building KDE4 is that
for me the qca2 library is installed with version 2.0 instead of 3.0.
make package fails with:
Error:
Alexandr Shadchin wrote:
On Thu, Dec 01, 2011 at 12:06:50PM -0600, Amit Kulkarni wrote:
On Thu, Dec 1, 2011 at 12:58 AM, Antoine Jacoutot ajacou...@bsdfrog.org
wrote:
On Thu, Dec 01, 2011 at 05:43:36AM +0600, Alexandr Shadchin wrote:
Hi,
This update package qca2 to the latest release
Hi,
This update package qca2 to the latest release 2.0.3.
Tested on amd64.
Comments ? OK ?
Considering this port is not hooked to the build, I think it's pretty safe...
ok aja@
this is used by KDE 4.X series alongwith qca-ossl. I will give it a
try while wading through the 4.8 beta1
On Thu, Dec 1, 2011 at 12:58 AM, Antoine Jacoutot ajacou...@bsdfrog.org wrote:
On Thu, Dec 01, 2011 at 05:43:36AM +0600, Alexandr Shadchin wrote:
Hi,
This update package qca2 to the latest release 2.0.3.
Tested on amd64.
Comments ? OK ?
Considering this port is not hooked to the build, I
On Thu, Dec 01, 2011 at 12:06:50PM -0600, Amit Kulkarni wrote:
On Thu, Dec 1, 2011 at 12:58 AM, Antoine Jacoutot ajacou...@bsdfrog.org
wrote:
On Thu, Dec 01, 2011 at 05:43:36AM +0600, Alexandr Shadchin wrote:
Hi,
This update package qca2 to the latest release 2.0.3.
Tested on amd64.
Hi,
This update package qca2 to the latest release 2.0.3.
Tested on amd64.
Comments ? OK ?
--
Alexandr Shadchin
Index: Makefile
===
RCS file: /cvs/ports/security/qca2/Makefile,v
retrieving revision 1.5
diff -u -p -r1.5 Makefile
On Thu, Dec 01, 2011 at 05:43:36AM +0600, Alexandr Shadchin wrote:
Hi,
This update package qca2 to the latest release 2.0.3.
Tested on amd64.
Comments ? OK ?
Considering this port is not hooked to the build, I think it's pretty safe...
ok aja@
--
Alexandr Shadchin
Index:
20 matches
Mail list logo
