I note the OpenRepository GitHub is read only intentionally to maintain
history of the overall son repo, and its intended that you'd fork it to
your own as the new master.
Adam
On Tuesday, 5 January 2016, Karen Etheridge wrote:
> Has the author been contacted to request
+1 from me too
On 5 January 2016 at 04:47, Richard Soderberg > wrote:
> +1 as a previous maintainer; for your sanity, I propose “0. Fix RT
> ticket 90183 and release it” (with the simple fix described by rjbs in
> that
Wow, wtf happened there.
snake - dmake... :)
Adam K
On Mon, Jul 4, 2011 at 9:08 AM, chm devel.chm...@gmail.com wrote:
On 7/1/2011 7:22 PM, Adam Kennedy wrote:
All mainstream win32 have snake now, they just don't have any other makes
What is snake? I don't seem to have it on
my winXP box
will be to make a declarative for OpenGL constructs that can be
sent straight to the hardware. Adam Kennedy has some work start in this
area (OpenGL::List).
Regards,
I've said nothing till now, because I figured more noise wouldn't help much.
But I quite like the rsync daemon/proxy idea, and as it so happens I'm
attending the OzLabs Unconference in 3 weeks time to hang out with
Tridge, Rusty and the other Australia C/Kernel/Samba/RSync elites.
So I'd be
On Wed, Feb 24, 2010 at 12:17 AM, Andreas J. Koenig
andreas.koenig.7os6v...@franz.ak.mind.de wrote:
On Tue, 23 Feb 2010 21:57:07 +1100, Adam Kennedy a...@ali.as said:
There is no reason to impose this kind of thing on end users, as the
failure does not actually prevent the module from
On Tue, Feb 23, 2010 at 9:13 PM, Andreas J. Koenig
andreas.koenig.7os6v...@franz.ak.mind.de wrote:
The signature test isn't really a test. Its not testing that the code
does its job, its testing that it passes its signature. Its not a
functionality test, its a security measure, and
You should not add MYMETA.yml to the MANIFEST, it will NEVER ship to CPAN.
Remove the signature test.
Adam K
On 23 February 2010 01:29, Hinnerk Altenburg hinn...@cpan.org wrote:
Hi,
I got problems with the MYMETA.yml and the recommended signature test from
2009/5/6 Jonathan Yu jonathan.i...@gmail.com:
The real question at hand here is: for modules that provide both a
Makefile.PL and Build.PL, which should be preferred? More than that,
from the perspective of CPAN authors, is it even useful to provide
both? Now that Module::Build is a core
I'll see to it that the pony goes into blead asap.
Adam K
2008/10/4 Nicholas Clark [EMAIL PROTECTED]:
On Sat, Oct 04, 2008 at 01:55:50PM +1000, Adam Kennedy wrote:
The magic ponies will be introduced in 5.8.9 and 5.10.1. You indeed
will never have to upgrade.
5.8.9 will ship, ponies ready
2008/10/3 Michael G Schwern [EMAIL PROTECTED]:
2008/9/30 Matt S Trout [EMAIL PROTECTED]:
If the world upgraded regularly, Module::Build wouldn't be such a disaster
anyway :)
Adam Kennedy wrote:
True, but it's FAR more palatable to say Just upgrade ONCE, and
you'll never have to think about
True, but it's FAR more palatable to say Just upgrade ONCE, and
you'll never have to think about it again compared to upgrading
continuously.
Adam K
2008/9/30 Matt S Trout [EMAIL PROTECTED]:
If the world upgraded regularly, Module::Build wouldn't be such a disaster
anyway :)
2008/9/30 Michael G Schwern [EMAIL PROTECTED]:
That said, people choose based on convenience, not abstract, long term safety.
So it's for the best that Module::Build absorb every convenience feature
from MI.
For the record, I concur entirely with this solution.
Module::Install was a step
2008/9/30 Michael G Schwern [EMAIL PROTECTED]:
chromatic wrote:
s/Module::Install/Autobundling/
Autobundling is fine for end-user all-in-one no-user-servicable-parts-inside
applications, but the CPAN is not the place for static linking. It would be
nice not to drag Perl kicking and
Vadim wrote:
Dear Douglas,
given that your CPAN module did not got proper evolving, would you mind
giving up on it and removing from CPAN?
I would like to publish a bridge module that connects Perl to different
Lisp implementations (CLISP, SBCL, CMUCL, GCL as a start), very much
like currently
Jonathan Rockway wrote:
Hi all,
I noticed search.cpan is acting differently now (probably due to the HOOO perl
fiasco). Were these changes discussed anywhere publicly before they were
made? I'm interested in a full list of changes, so I don't have to guess
what they are. (I'm a /little/
Looking at mine (ADAMK) which has a relatively large sample of modules
to intuit patterns from, I'd say that that Debian modules are created
and updated by hand, and there's a relatively large number of volunteers.
But the module versions do slip, and my less popular modules are not
packaged.
Eric Wilhelm wrote:
# from Sébastien Aperghis-Tramoni
# on Tuesday 17 April 2007 05:12 pm:
If you really want Module::Build to be installed, why not simply
create a traditional Makefile.PL and add Module::Build as a
prerequisite? That way your module can be installed with
Gabor Szabo wrote:
On 3/18/07, David Golden [EMAIL PROTECTED] wrote:
You might find this open book helpful:
http://www.oreilly.com/catalog/osfreesoft/book/
thanks
8. Aggregation of this Package with a commercial distribution is always
permitted provided that the use of this Package is
Dariusz Dwornikowski wrote:
On 2007-01-04, at 03:36, Chris wrote:
On Wed, 3 Jan 2007, brian d foy wrote:
In article [EMAIL PROTECTED], Dariusz Dwornikowski
[EMAIL PROTECTED] wrote:
hi,
Sincu You seem not to be interested in updating the module
anymore, I would like to upload a
Johan Vromans wrote:
Jonathan Rockway [EMAIL PROTECTED] writes:
Why don't y'all just use Module::Install?
Because it doesn't perform a mere install, as the name suggests. It
builds, meaning it requires (and uses) a build environment -- and
scares away customers that do not want to have a
Ricardo SIGNES wrote:
* brian d foy [EMAIL PROTECTED] [2007-03-04T12:09:26]
I'm not talking about the particular field name, but the idea that I'd
want to say in META.yml Don't send me mail, or whatever setting I
want.
Instead of having to disable (or enable) CC for every new tool, I'd
want a
Chris Dolan wrote:
Personally, The best solution is to have an official policy for adding
non-standard additions. X- is bad for reasons that many people have
shared. I like the idea of a per-module special prefs area. To insure
that collisions are impossible, how about a URI for the prefs
Eric Wilhelm wrote:
# from Chris Dolan
# on Sunday 04 March 2007 11:44 am:
To insure that collisions are impossible, how about a URI for
the prefs wrapper like below (sorry, not sure if this is valid YAML)
extensions:
'http://search.cpan.org/dist/CPAN-Reporter/':
cc_author:
As of 5.10, use constant will use less memory than Greg's version.
I'm loathe to make the same changes for 5.8.9, as the implementation
confuses some modules that inspect the symbol table. The necessary
infrastructure will be in 5.8.9 though.
You can add me to the don't want to see it happen
I would rather just lobby for cc_author being added to the spec with
a very simple binary option rather than see a whole extension system
built.
cc_author: 0
Or even -- in a CPAN::Reporter independent style -- something like this:
cc_author:
pass: 0
fail: 1
unknown: 1
na: 0
So
(Andreas J. Koenig) wrote:
On Wed, 7 Feb 2007 22:11:43 -0800, Joshua ben Jore [EMAIL PROTECTED] said:
I'd just read of Time::Cube, a disjointed rant full of hate speech.
This is the kind of content that is most deserving of deletion from
CPAN. Would the responsible parties please go
Hmm, it looks like there is a strong correspondence between distros
using 'directory' and distros produced by Module::Install. There goes
Adam, breaking rules and rebelling against established conventions.
Hehe. Just kidding. I think I like 'directory' better myself anyway.
Sigh, one of
B/BL/BLM/Win32API-Registry-0.27
I can move this one pretty easily too, it needs a new release anyway.
R/RC/RCAPUTO/POE-0.3502
R/RC/RCAPUTO/POE-Component-Client-Keepalive-0.0801
I'm pretty sure Rocco will move next release as well.
Adam K
29 matches
Mail list logo