nyone have any other recommendations or concerns
before I upload it to PAUSE?
Thanks!
--
Sean Quinlan <[EMAIL PROTECTED]>
t;
> An alternative might be the User:: namespace. Maybe User::Admin::User
> and User::Admin::Group?
>
> Any opinions or pointers to similar things?
>
> Thanks,
>
> d.
--
Sean Quinlan <[EMAIL PROTECTED]>
Massachusetts General Hospital
signature.asc
Description: This is a digitally signed message part
, allowing for Backup::PostgreSQL,
etc. down the line? Or should such things stay under specific server
namespaces?
[trying to catch up after being away all day]
--
Sean Quinlan <[EMAIL PROTECTED]>
Massachusetts General Hospital
signature.asc
Description: This is a digitally signed message part
your databases backed up as well in a coma
# seperated list:
# days: Mon,Wed,Sat
# For most sites, once a week + daily logs is probably sufficient
backup:
databases:
- mysql
days: Sat
--
Sean Quinlan <[EMAIL PROTECTED]>
MySQL-Backup-0.8.tar.gz
Description: application/compressed-tar
signature.asc
Description: This is a digitally signed message part
ing it bouncing around in my head!
;-}
Perhaps DBA::Backup::MySQL? The DBA name space could then be a catch all
for any tools specifically targeted at database administration tasks,
such as backups.
--
Sean Quinlan <[EMAIL PROTECTED]>
Massachusetts General Hospital
signature.asc
Description: This is a digitally signed message part
ncepts
> across databases.
>
> You'll either end up with a lowest-common-denominator approach that
> has too little functionality, or have so many database-specific
> flags an options and whatnot that there's little benefit in having
> a "common API".
>
&g
general
consensus, keep the modules on CPAN current, or use email/lists/etc. and
only update CPAN at significant development points.
Thanks!
--
Sean Quinlan <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
x27;ll just put new tarballs on my own website, and
wait for more significant checkpoints to update CPAN.
> That said, I think regular uploads to CPAN won't really hurt anything.
> It just won't help too much.
>
> Chris
>
> On Nov 10, 2004, at 10:57 AM, Sean Quinlan
e 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)?
Many thanks!!
--
Sean Quinlan <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
On Thu, 2004-11-11 at 10:20, Christopher Hicks wrote:
> 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
trol system.
...
That being said, someday having one available tied to CPAN could be very
cool under these types of circumstances.
--
Sean Quinlan <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
On Tue, 2005-03-15 at 18:09 -0600, Eric Wilhelm wrote:
> Would anti-pollution laws help or hurt CPAN?
In this community I get the sense that even mentioning laws can be bad.
But I don't see how some strong encouragement would hurt. ;)
Personally I think any author should continue to be able to up
l enough. If it includes a good
paragraph or two of description and examples would be quite useful,
IMHO.
--
Sean Quinlan <[EMAIL PROTECTED]>
Massachusetts General Hospital
signature.asc
Description: This is a digitally signed message part
n) to reset any hard-coded or config-file variable.
And is why, if I want a user to set a value, I use 'foo=i' or 'foo=s' or
such. That seems far more natural to me, and has worked quite well in my
experience. What user, who might be confused by --foo --no-foo handling,
is going to even _know_ that --no-foo is an option?!?
--
Sean Quinlan <[EMAIL PROTECTED]>
Massachusetts General Hospital
14 matches
Mail list logo
