Glyn Astill <glynastill at yahoo.co.uk> writes:
>> Slony release when main devs think it is time to do, and as you
>> said, 
>> perltools are not maintain by core-dev. 
>> I find them usefull for my first approach of slony and wish them to
>> keep 
>> up-to-date, or *at least* to be sync with a specific release. So,
>> looking at 
>> the slony 'roadmap', perhaps it can be better to push tools scripts
>> to 
>> another place : a pgfoundry or a slony-tools-1.2.X.tar. 
>> Then, it let 'mature users' get the core, and other users get the 
>> contrib-tools wich are *sync* and released with slony versions.
>> 
>> I prefer have to wget slony-1.2.13, slony-doc-1.2.13,
>> slony-tools-1.2.13 
>> archives, but be sure they work all together. Than getting one
>> package with 
>> doc from 1.2.12, tools between 1.1 and 1.2.12 and core from 1.2.13.
>> 
>> It can consolidate them by releasing each part singly (even if at
>> the same 
>> time).
>> 
>> Views ?
>
> I've never used the perl tools, partially out of laziness and
> partially out of not seeing the need. Instead I just write little
> slonik scripts. Do they really save much time?

The original point of the "altperl" scripts was as something of a
crutch for people that were having a hard time wrapping their heads
around the slonik language.

Over time, some of Afilias' staff has progressed from valuing the
altperl scripts to thinking them pointless because "slonik isn't that
hard to write."  (I'm certainly in that camp, but I don't consider
myself terribly representative since I have written quite a lot of
code that generates slonik code! :-))
-- 
(reverse (concatenate 'string "ofni.sesabatadxunil" "@" "enworbbc"))
http://www3.sympatico.ca/cbbrowne/oses.html
As usual,  this being  a 1.3.x release,  I haven't even  compiled this
kernel yet.   So if it works,  you should be  doubly impressed. (Linus
Torvalds, announcing kernel 1.3.3 on the linux-kernel mailing list.)