RE: Distribution version vs. Main package version
Well... You should either rename this thing or advertise more :) -Original Message- From: Ricardo SIGNES [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 11, 2008 1:51 AM To: module-authors@perl.org Subject: Re: Distribution version vs. Main package version * Paul Johnson [EMAIL PROTECTED] [2008-11-10T17:17:22] I'm starting to get annoyed by the extraneous commits into the revision control system. And so I'm considering the option of not having the version number in the file that gets checked in, but expanding it for a release. Using Dist::Zilla, there is no extraneous commit. $VERSION assignment is added at 'make dist' time by dzil. The single canonical source for dist version is the dist configuration file. -- rjbs
Re: Distribution version vs. Main package version
In general configuration mgt thought there is the version of the distribution and that in turn consists of a set of revisions of components. Bumping the revision # of everything makes for configuration management nightmares. AFAIK subversion and RCS work this way. I saw it first 20 years ago on Polytron PVCS --Original Message-- From: Ricardo SIGNES Sender: To: module-authors@perl.org Sent: Nov 10, 2008 4:43 PM Subject: Re: Distribution version vs. Main package version * Jonas Brømsø Nielsen [EMAIL PROTECTED] [2008-11-10T16:15:20] I like to be able to release distributions without necessarily touching a code module, if changes are just documentation, tests or other files. I only update package versions when code/functionality changes, so developers using my module can depend on this version number, when examining APIs, bugs etc. I use perl-reversion (part of Perl-Version) or Dist::Zilla to keep the same version on every .pm file and the dist. It's a little annoying that the version changes on things that are unchanged, but it keeps life simple. -- rjbs Sent from my BlackBerry® smartphone with Nextel Direct Connect
RE: Package aliases and isa()
You are clobbering Gtk2::Pango symbol table and trying to implement and
check is-a relationship, which is OO stuff. I just checked Gtk2::Pango and
it seems to consist of only constants. So, IMO, you can just say:
package Gtk2::Pango;
#...
use Pango; # import all constants into Gtk2::Pango
our @EXPORT = @Pango::EXPORT;
1;
-Original Message-
From: Torsten Schoenfeld [mailto:[EMAIL PROTECTED]
Sent: Sunday, November 09, 2008 6:59 PM
To: module-authors@perl.org
Subject: Package aliases and isa()
Aloha,
over in gtk2-perl land, we'd like to split out the Gtk2::Pango stuff from
the
Gtk2 module into its own module with the namespace Pango. We would like to
do
this in a backwards compatible way so that any code that is using the
Gtk2::Pango stuff continues to work just fine when we switch Gtk2 over to
use
the new Pango.
So we basically do this in Gtk2.pm:
use Pango;
{
no strict 'refs';
foreach my $key (keys %Pango::) {
*{'Gtk2::Pango::' . $key} = *{'Pango::' . $key};
}
}
For some reason, this has the effect that the following lines both evaluate
to true:
Pango::Layout-isa (Gtk2::Pango::Layout::);
Gtk2::Pango::Layout-isa (Pango::Layout::);
Now, that's really good because we need those to evaluate to true for
backwards
compatibility. The problem is that I don't understand *why* they are true.
I attach a simple standalone program that demonstrates this behavior. perl
5.8.8, 5.10.0, and blead all output two 1s when running this program on my
machine. perl 5.6.2, however, evaluates New-isa(Old::) to false.
So I wonder if it is safe to rely on the behavior exhibited by perl = 5.8.
Or
is it just some implementation-dependent artifact? Is there a better way to
achieve what I want?
-Torsten
Re: Distribution version vs. Main package version
* Burak Gürsoy [EMAIL PROTECTED] [2008-11-11T14:25:27] Well... You should either rename this thing or advertise more :) I'll advertise more when it's stabler. -- rjbs
