On Oct 1, 2009, at 7:41 AM, Josh Susser wrote:
On Sep 30, 2009, at 11:44 PM, John Barnette wrote:
I'd like to add an error to Specification#validate if the spec's
name doesn't match /[a-z][a-z0-9-_]*/i. Any objections?
Disregarding obviously malformed specs, all current gem names match.
On Sep 30, 2009, at 11:44 PM, John Barnette wrote:
I'd like to add an error to Specification#validate if the spec's
name doesn't match /[a-z][a-z0-9-_]*/i. Any objections? Disregarding
obviously malformed specs, all current gem names match.
Sounds good, with one minor nitpick: your regexp
On Thu, Oct 1, 2009 at 8:44 AM, John Barnette wrote:
> All,
>
> I'd like to add an error to Specification#validate if the spec's name
> doesn't match /[a-z][a-z0-9-_]*/i. Any objections? Disregarding obviously
> malformed specs, all current gem names match.
>
No objection from here, that will red
On Wed, Sep 30, 2009 at 11:44 PM, John Barnette wrote:
> All,
>
> I'd like to add an error to Specification#validate if the spec's name
> doesn't match /[a-z][a-z0-9-_]*/i. Any objections? Disregarding obviously
> malformed specs, all current gem names match.
That sounds like a good idea.
___
All,
I'd like to add an error to Specification#validate if the spec's name
doesn't match /[a-z][a-z0-9-_]*/i. Any objections? Disregarding
obviously malformed specs, all current gem names match.
~ j.
___
Rubygems-developers mailing list
http://r
