On Dec 10, 2010, at 2:43 PM, Dimitri Fontaine wrote: > "David E. Wheeler" <da...@kineticode.com> writes: >> You keep making extension authors have to do more work. I keep trying >> to make it so they can do less. We want the barrier to be as low as >> possible, which means a lot of DRY. Make it *possible* to do more >> complicated things, but don't *require* it. > > Sorry, imposing that - ain't part of the version number string won't > make any impression on me as far as getting simple is concerned. Go find > a single debian package not having - in its version number, and that's a > native software (developed to build debian).
I'm making no such imposition. I'd rather it not be in contrib version numbers, because they should adhere to PostgreSQL-standard version numbering IMHO. YOu can use any characters you want in the version string. The upgrade file names simply start with "$extension-", so the format is "$extension-$version.sql". That's it. > For details, see the following, then explain me how RPM is so > differently simple, and then why I should care. > > http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-f-Version > > So really, using %v to say "put the current version number here" does > not seem like a problem for me, it allows me not to have to think about > *any* files naming rules nor version numbering scheme. It's just not necessary. Best, David -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
