Since 2009-12-09 we have slony1-1.2.20 , and there is also slony1-2.0.2 , maybe it should be slotted ebuilds? Reproducible: Always
Anybody home?;)
Is there any reason to have both on the same system at the same time? (Besides a desire to have testing and production on the same machine.) Will a simple name change of the ebuild do for a version bump, or is there something more that needs to be done? What about for version 2.0.4?
As I know, version 1.2.x is incompatible to 2.x. people using 1.2.x should have this version for some time.
+ 11 Apr 2011; Patrick Lauer <patrick@gentoo.org> +slony1-1.2.22.ebuild, + +slony1-2.0.6.ebuild: + Bump, adding 2.0, fixes #306369 Please beat it up as much as you can, I haven't tested it more than simple "yeah, seems to kinda do something" :)
FYI slony1-2.0.6 is unusable due to http://bugs.slony.info/bugzilla/show_bug.cgi?id=220
Created attachment 278749 [details] improved slony1-2.0.6 ebuild with patch Improved ebuild for 2.0.6. No current slony ebuild plays well with slotted postgresql. I've added proper detection of pg paths for configure options rather than hard coding. Also added a patch.
Created attachment 278751 [details, diff] patch that goes with slony1-2.0.6-r1 Patch to match http://git.postgresql.org/gitweb?p=slony1-engine.git;a=blobdiff;f=src/slonik/slonik.c;h=f0af6a9a0eb9a2ec14408d917627d96df8b44070;hp=249d944bbadf48a06525a5916a0600573d18dc97;hb=8f681a8cb06571396b8e99be220a38f92f1d3baf;hpb=a3df6bedcf40abbc6f2bbb7da1d21eb835aac252
The Slony's configure script finds the proper paths just fine without help, and upstream's bug 220 is resolved-fixed in version 2.0.7.
It is your perogative to reject my ebuild that provides the proper paths up front but why keep specifying the wrong path? myconf="${myconf} --with-pgincludedir=/usr/include/postgresql/pgsql" That line from slony1-2.0.6.ebuild is plain wrong. At the least, if we want to trust the packages ./configure to guess the right stuff we should not try to mislead it.
(In reply to comment #9) > It is your perogative to reject my ebuild that provides the proper paths up > front but why keep specifying the wrong path? > myconf="${myconf} --with-pgincludedir=/usr/include/postgresql/pgsql" > That line from slony1-2.0.6.ebuild is plain wrong. At the least, if we want to > trust the packages ./configure to guess the right stuff we should not try to > mislead it. I didn't and won't fix the ebuild for 2.0.6, but I did fix it for the ebuild in 2.0.7.
