On Thu, 2004-11-11 at 03:29, Sean Quinlan wrote:
On Wed, 2004-11-10 at 19:35, _brian_d_foy wrote:
You can mark distributions as developer releases, upload
as appropriate, and delete distributions when you don't need
them any more. :)
Thanks, sounds perfect! I looked around PAUSE though
On Nov 10, 2004, at 10:57 AM, Sean Quinlan wrote:
Just wondering about appropriate PAN usage. I have a set of modules I'm
working on on an almost daily basis. They are alpha's currently (the
port from the working MySQL::Backup to DBA::Backup
DBA::Backup::mysql). I talked about them at our local
On Wed, 10 Nov 2004, Sean Quinlan wrote:
How do we mark uploads as a dev release? Can it be done after it's
uploaded or is it something in the release before upload that indicates
it (I browsed YAML .49_01 and didn't see anything)?
The underscore in the filename is the flag. (Its right there
# The following was supposedly scribed by
# Ken Williams
# on Thursday 11 November 2004 09:08 am:
IMO if people are doing any sort of collaboration, you really should
set up a centralized source that they can submit patches against,
and keep up-to-the-minute track of what you're doing (like
[[ This message was both posted and mailed: see
the To, Cc, and Newsgroups headers for details. ]]
In article [EMAIL PROTECTED], Sean Quinlan
[EMAIL PROTECTED] wrote:
On Wed, 2004-11-10 at 19:35, _brian_d_foy wrote:
You can mark distributions as developer releases, upload
as appropriate,
I've made some changes to this since we had last discussed it. The
new methods allow you to do without a main::usage() subroutine, and
provide some DWIM functionality. Sorry, it is not on CPAN yet.
Any feedback on the interface/usability would be appreciated. Below
is the synopsis, the code
