search

chrisburel / perlqt4

Automatically exported from code.google.com/p/perlqt4
Other
0 stars 0 forks source link

not on cpan? #49

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
I may be missing something, but the only version of perlqt4 I can find on cpan 
is a years old developer release.

Any reason why more recent perlqt4 can't be installed via CPAN?

Thanks in advance.

Original issue reported on code.google.com by skibrian...@gmail.com on 16 Oct 2012 at 3:54

GoogleCodeExporter commented 9 years ago 
There were a couple problems.

#1. I'm not the same person as the author for PerlQt3, so I don't own the Qt 
namespace on CPAN.  I sent mail to both the original maintainer and to the CPAN 
admins a while ago, and both mails got no response.

#2. The release tarball contains all the example code, which has been ported 
from the Qt C++ examples.  These use the original class names from the 
examples, which are really generic, like "Calculator" and "Connection".  CPAN 
thinks I'm trying to be sneaky and reimplement modules that I don't own, so it 
rejects the entire tarball.

#3.  I've been versioning PerlQt4 independently of the versions of PerlQt3.  
So, the latest release of PerlQt3 is 3.008.  But my latest release is 0.96.0 (I 
think there may be a later version uploaded to my user area (cburel) in CPAN).  
So CPAN sees the current release of Qt (3.008) is greater than the one that I'm 
uploading (0.96.0), and thinks that this is an older version than the latest.  
At the time, it just seemed strange to me to jump from 0.96.0 to 4.0.

So, there's a bunch of red tape that never got sorted out.

Original comment by chrisbu...@gmail.com on 16 Oct 2012 at 6:40

GoogleCodeExporter commented 9 years ago 
There appears to be this on CPAN:

  Alien-QtSmoke-4.3.3       15 Dec 2009
  Alien-SmokeQt-4.6.0.4     18 Mar 2011
  Qt-0.96.0             19 Mar 2011
  Qt4-0.99.0            14 Feb 2012

On FreeBSD the port you appear to want is devel/kdebindings4-perl-perlqt; this 
installs 0.96.0 (source: grepping for 'VERSION' in your modules). However, on 
Win32 there were compilation problems which happened on or about Feb 2012, so 
logically on Win32 it seems you want Qt4-0.99.0. 

Can you maybe attach a note somewhere on CPAN and clear up this confusion? :) 
If you can't do that, would you be willing to clarify in this issue? I'm 
personally trying to get Qt working on FreeBSD and windows. Thanks.

Original comment by d...@jetcafe.org on 3 Jan 2013 at 6:32

GoogleCodeExporter commented 9 years ago 
Looks like I never responded to this, sorry about that.

Re: #1, I'd say the right thing is to use the QT4 namespace. That also lets you 
skip worrying about the versioning.

Re: #2, why not simply put those examples to the QT4::Example::.* namespace?

Hope that helps!

Cheers,
Brian Szymanski

Original comment by skibrian...@gmail.com on 4 Jan 2013 at 12:12

GoogleCodeExporter commented 9 years ago 
perl-Qt-0.96.0 is really painfull to handle in distros as it looks older than 
perl-Qt-3.x

Why not using the same naming convention as the Qt package: lower case qt with 
major version appended?

By that way we could have perl-qt4-0.96.0 and we could even obsolete 
perl-Qt-3.x (which should have been named perl-qt3-3.x BTW)

Aside that, that would be cool to have perl-Qt in it's own perl directory:
/usr/lib64/perl5/vendor_perl/Qt4/*.pm (calling modules like Qt4::QtCore4)
By that way , we could have several perl-qt versions installed at the same time 
in the system, and that would greatly ease migration developpemtns.

My 2 cents.

Original comment by olivier....@gmail.com on 7 Jul 2014 at 8:53