Olivier Mengu? wrote:
- I published the HPUX distro in 2009 just a few weeks before losing access
to an HP-UX system:
Bummer. Fortunately there are people around with access who I can bug.
Tux does HP-UX smokes, and would probably be willing to run probe code
for me.
- the current dependencies
2011/9/25 Zefram zef...@fysh.org
I'd particularly like
to know whether the new DT:TZ:Local code behaves itself on Windows, VMS,
HP-UX, and AIX.
The new implementation of DT:TZ:Local has implementations for all platforms
in a single unit. I don't like the fact that much code is compiled and
Karen Etheridge wrote:
So, if you're not going to generate a pod that contains this list at build-
or install-time, please provide an executable (App::Cmd is nice!) that
generates the list on the fly.
Thanks for the comments. I'm leaning towards the command-line tool
approach.
-zefram
Dave Rolsky wrote:
Why borg the Windows and HP-UX code into this distro instead of letting
other maintainers handle this?
I don't think there's significant value in having separate distros here.
Having a single distro has the distinct advantages that the behaviour
is consistent: you just
Dave Rolsky wrote:
Why borg the Windows and HP-UX code into this distro instead of letting
other maintainers handle this?
I don't think there's significant value in having separate distros here.
Having a single distro has the distinct advantages that the behaviour
is consistent: you just
I wrote:
I've got plans for DT:TZ:Local.
Another strand of this that might be of interest. I got thinking
about the various mechanisms we have that try to DWIM with a ruleless
SystemV-style zone spec (such as GMT0BST). The Olson database has
the main US ones as links to appropriate geographical
auta...@urth.org wrote:
I'd like to hear from David Pinkowitz and Olivier Mengue on this.
Sure.
I'd be fine with new names for utility subs like this. Obviously there'd have
to be a deprecation period.
I'm not intending to ever remove the old interfaces. They're cheap to
retain indefinitely.
On Mon, 26 Sep 2011, auta...@urth.org wrote:
As to how and when these docs get generated, I don't really care, I just
want the docs to be available after the distro is installed. If you want
to do that as part of the install process that's fine.
Actually, thinking about this a bit more, I
Dave Rolsky wrote:
Actually, thinking about this a bit more, I really think it's a good idea
to generate it as part of building the distro. That way these docs will
be available from metacpan.org and s.c.o.
That'll be even more out of date than generating it at install time,
if that's done in
On Mon, 26 Sep 2011, Zefram wrote:
Dave Rolsky wrote:
Actually, thinking about this a bit more, I really think it's a good idea
to generate it as part of building the distro. That way these docs will
be available from metacpan.org and s.c.o.
That'll be even more out of date than generating
Dave Rolsky wrote:
That information isn't easily accessible on a system in any other
way that I know of.
It's supplied in data structures in T:OTZ:D or DT:TZ:Olson. Including the
parts that aren't represented in the old DT:TZ:Catalog data structures.
As I said earlier, it's easy to write
On Mon, Sep 26, 2011 at 05:45:30PM +0100, Zefram wrote:
Dave Rolsky wrote:
That information isn't easily accessible on a system in any other
way that I know of.
It's supplied in data structures in T:OTZ:D or DT:TZ:Olson. Including the
parts that aren't represented in the old
auta...@urth.org wrote:
the ideal would be to include the zone and the invalid local time in the
message.
I've just uploaded DT:TZ:SystemV 0.005 to CPAN, and it does this:
$ perl -MDateTime::TimeZone::SystemV -MDateTime -lwe 'print
On Sun, 25 Sep 2011, Zefram wrote:
This is a total rewrite of DateTime::TimeZone. The main purpose of the
change is that, as we've discussed for the past couple of years, it uses
DT:TZ:Olson (and thus the standard tzfiles) for Olson zones. It ought
to be a drop-in replacement for the existing
14 matches
Mail list logo
