Re: Removing Libraries (Was: Re: [HACKERS] Open 7.3 issues)
Actually, I think Jeroen T. Vermeulen [EMAIL PROTECTED] should create the project. It is his code, and if he would add me as an admin, that would help. I am CC'ing him. --- Marc G. Fournier wrote: On Sun, 18 Aug 2002, Peter Eisentraut wrote: Marc G. Fournier writes: Okay, here is what I'd like to suggest ... Bruce, let's start off really simple ... go create a project for libpq++ (I believe someone even volunteered to maintain it?) and let me know once created, and I'll move the CVS directory over for libpq++ and out of the pgsql-server directory I said that I would lend a hand in preparing the build system, but I'm not going to start a project on gborg if I have to agree to a two-page terms of service agreement and I don't get to choose the exact wording of the license. I didn't ask you to, I asked Bruce to ... and the license should stay BSD ... -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: Removing Libraries (Was: Re: [HACKERS] Open 7.3 issues)
Oh, sorry. I will do it now. --- Marc G. Fournier wrote: We're talking about libpq++, not libpqxx :) On Mon, 19 Aug 2002, Bruce Momjian wrote: Actually, I think Jeroen T. Vermeulen [EMAIL PROTECTED] should create the project. It is his code, and if he would add me as an admin, that would help. I am CC'ing him. --- Marc G. Fournier wrote: On Sun, 18 Aug 2002, Peter Eisentraut wrote: Marc G. Fournier writes: Okay, here is what I'd like to suggest ... Bruce, let's start off really simple ... go create a project for libpq++ (I believe someone even volunteered to maintain it?) and let me know once created, and I'll move the CVS directory over for libpq++ and out of the pgsql-server directory I said that I would lend a hand in preparing the build system, but I'm not going to start a project on gborg if I have to agree to a two-page terms of service agreement and I don't get to choose the exact wording of the license. I didn't ask you to, I asked Bruce to ... and the license should stay BSD ... -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: Removing Libraries (Was: Re: [HACKERS] Open 7.3 issues)
Done. Called libpq++. --- Bruce Momjian wrote: Oh, sorry. I will do it now. --- Marc G. Fournier wrote: We're talking about libpq++, not libpqxx :) On Mon, 19 Aug 2002, Bruce Momjian wrote: Actually, I think Jeroen T. Vermeulen [EMAIL PROTECTED] should create the project. It is his code, and if he would add me as an admin, that would help. I am CC'ing him. --- Marc G. Fournier wrote: On Sun, 18 Aug 2002, Peter Eisentraut wrote: Marc G. Fournier writes: Okay, here is what I'd like to suggest ... Bruce, let's start off really simple ... go create a project for libpq++ (I believe someone even volunteered to maintain it?) and let me know once created, and I'll move the CVS directory over for libpq++ and out of the pgsql-server directory I said that I would lend a hand in preparing the build system, but I'm not going to start a project on gborg if I have to agree to a two-page terms of service agreement and I don't get to choose the exact wording of the license. I didn't ask you to, I asked Bruce to ... and the license should stay BSD ... -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: Removing Libraries (Was: Re: [HACKERS] Open 7.3 issues)
Marc G. Fournier writes: Okay, here is what I'd like to suggest ... Bruce, let's start off really simple ... go create a project for libpq++ (I believe someone even volunteered to maintain it?) and let me know once created, and I'll move the CVS directory over for libpq++ and out of the pgsql-server directory I said that I would lend a hand in preparing the build system, but I'm not going to start a project on gborg if I have to agree to a two-page terms of service agreement and I don't get to choose the exact wording of the license. I would prefer it if libpq++ would stay in the cvs tree at cvs.postgresql.org. There's no point in starting an entirely new infrastructure elsewhere. -- Peter Eisentraut [EMAIL PROTECTED] ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: Removing Libraries (Was: Re: [HACKERS] Open 7.3 issues)
On Sun, 18 Aug 2002, Peter Eisentraut wrote: Marc G. Fournier writes: Okay, here is what I'd like to suggest ... Bruce, let's start off really simple ... go create a project for libpq++ (I believe someone even volunteered to maintain it?) and let me know once created, and I'll move the CVS directory over for libpq++ and out of the pgsql-server directory I said that I would lend a hand in preparing the build system, but I'm not going to start a project on gborg if I have to agree to a two-page terms of service agreement and I don't get to choose the exact wording of the license. I didn't ask you to, I asked Bruce to ... and the license should stay BSD ... ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Removing Libraries (Was: Re: [HACKERS] Open 7.3 issues)
On Thu, 15 Aug 2002, Peter Eisentraut wrote: integrate or remove new libpqxx integrate or add to gborg Pg:DBD Seems like gborg is the place for these. I would volunteer to package libpq++ separately. Okay, the procedure is simple, but where do we want to put this? Do we want to move the extracted libraries over to gborg (would be my first preference), or keep them in the core repository? Regardless of which, the extraction is simple ... but if GBorg, if you go over and make a project and let me know what it is, I can move the library from our CVS repository straight over there, so that we lose no logs or anything ... just let me know its created ... Bruce, can you make a project for Pg::DBD? ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: Removing Libraries (Was: Re: [HACKERS] Open 7.3 issues)
Marc G. Fournier wrote: On Thu, 15 Aug 2002, Peter Eisentraut wrote: integrate or remove new libpqxx integrate or add to gborg Pg:DBD Seems like gborg is the place for these. I would volunteer to package libpq++ separately. Okay, the procedure is simple, but where do we want to put this? Do we want to move the extracted libraries over to gborg (would be my first preference), or keep them in the core repository? Regardless of which, the extraction is simple ... but if GBorg, if you go over and make a project and let me know what it is, I can move the library from our CVS repository straight over there, so that we lose no logs or anything ... just let me know its created ... Bruce, can you make a project for Pg::DBD? OK, I am ready to do the work, but I would like to get a plan of where we are going. I see in interfaces: cli ecpg jdbc libpgeasy libpgtcl libpq libpq++ libpqxx odbc perl5 python and we have Pg:DBD waiting to be added. Now, I know one of Marc's goals is to have libpq as a stand-alone tarball, but I thought we decided that this _didn't_ require it to be in a separate CVS repository. If we split these up based on activity, we have, in decreasing activity order: jdbc odbc libpq libpqxx cli ecpg libpq++ libpgtcl python libpgeasy Pg:DBD perl5 We already have separate web sites for jdbc and odbc, and they are in our main CVS. What goals do we have? Do we create gborg accounts for all/most of these so releases can be made independently of the main server? Do we move their CVS out of the main tree too? I don't think we should judge libpqxx differently than the other interfaces just because it is new. We should find a consistent solution and apply that to all of these interfaces. Let me add that odbc and jdbc have successfully made releases independent of our server for over a year now. I wonder if the best solution is to create gborg accounts for every interface and keep them in our main CVS, and do independent releases from there. Should we point to jdbc/odbc.postgresql.org from gborg? -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: Removing Libraries (Was: Re: [HACKERS] Open 7.3 issues)
Bruce Momjian [EMAIL PROTECTED] writes: Now, I know one of Marc's goals is to have libpq as a stand-alone tarball, but I thought we decided that this _didn't_ require it to be in a separate CVS repository. Removing libpq is impossible since psql, pg_dump, etc all depend on it. I don't think we should judge libpqxx differently than the other interfaces just because it is new. The fact that it is new is a strike against it, and the fact that it is not integrated is a bigger strike against it. I think we should move out libpqxx and libpq++ now, and also perl5 if we are going to put DBD::Pg on gborg rather than in the main distro. We want to ensure there is a level playing field for libpqxx and DBD::Pg. jdbc and odbc should be moved if and only if their maintainers want it. I'm not in a hurry to move the rest; they're small and don't generate a lot of CVS traffic. regards, tom lane ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: Removing Libraries (Was: Re: [HACKERS] Open 7.3 issues)
Marc G. Fournier [EMAIL PROTECTED] writes: Bruce, can you make a project for Pg::DBD? Erm, has anyone contacted the maintainer of DBD::Pg? Given that Bruce doesn't maintain it and AFAIK Jeffrey Baker (the current maintainer) and hasn't expressed any dissatisfaction with CPAN, I'm not sure why you'd like to move the software to GBorg... Cheers, Neil -- Neil Conway [EMAIL PROTECTED] PGP Key ID: DB3C29FC ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: Removing Libraries (Was: Re: [HACKERS] Open 7.3 issues)
Neil Conway wrote: Marc G. Fournier [EMAIL PROTECTED] writes: Bruce, can you make a project for Pg::DBD? Erm, has anyone contacted the maintainer of DBD::Pg? Given that Bruce doesn't maintain it and AFAIK Jeffrey Baker (the current maintainer) and hasn't expressed any dissatisfaction with CPAN, I'm not sure why you'd like to move the software to GBorg... Uh, I got OK from Edmund. I haven't talked to Jeffrey but I thought someone else had. I thought he had just taken it over and was OK with us handling it. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: Removing Libraries (Was: Re: [HACKERS] Open 7.3 issues)
On Sat, 17 Aug 2002, Bruce Momjian wrote: OK, I am ready to do the work, but I would like to get a plan of where we are going. I see in interfaces: cli ecpg jdbc libpgeasy libpgtcl libpq libpq++ libpqxx odbc perl5 python and we have Pg:DBD waiting to be added. Now, I know one of Marc's goals is to have libpq as a stand-alone tarball, but I thought we decided that this _didn't_ require it to be in a separate CVS repository. Ya, this one I had no problem with ... the only thing with libpq that I do request is that it has its own configure so that it can be completely standalone ... but, IMHO, if someone compiles the server, they are going to need libpq, I just want to make sure taht if they want libpq, they don't need the server ... If we split these up based on activity, we have, in decreasing activity order: jdbc odbc libpq libpqxx cli ecpg libpq++ libpgtcl python libpgeasy Pg:DBD perl5 We already have separate web sites for jdbc and odbc, and they are in our main CVS. What goals do we have? Do we create gborg accounts for all/most of these so releases can be made independently of the main server? Do we move their CVS out of the main tree too? IMHO, yes ... Let me add that odbc and jdbc have successfully made releases independent of our server for over a year now. Correct, so they should be the easiest to move out as well ... I wonder if the best solution is to create gborg accounts for every interface and keep them in our main CVS, and do independent releases from there. Should we point to jdbc/odbc.postgresql.org from gborg? Chris has made code changes to GBorg to allow for this based on requests from Dave Page (ie. PgAdminII) ... so there is no problems with that ... As for keeping them in our main CVS, the more we put over onto GBorg, the more it will get used, test, debugged, pounded and stabilized ... hell, maybe some of the 'dead projects' that are on GBorg will come alive again also if ppl are going to GBorg and find them, download them and hit the authors for fixes :) But, moving the interfaces over will at least give ppl a reason to go over and see what is there ... ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: Removing Libraries (Was: Re: [HACKERS] Open 7.3 issues)
On Sat, 17 Aug 2002, Tom Lane wrote: Bruce Momjian [EMAIL PROTECTED] writes: Now, I know one of Marc's goals is to have libpq as a stand-alone tarball, but I thought we decided that this _didn't_ require it to be in a separate CVS repository. Removing libpq is impossible since psql, pg_dump, etc all depend on it. I don't think we should judge libpqxx differently than the other interfaces just because it is new. The fact that it is new is a strike against it, and the fact that it is not integrated is a bigger strike against it. I think we should move out libpqxx and libpq++ now, and also perl5 if we are going to put DBD::Pg on gborg rather than in the main distro. We want to ensure there is a level playing field for libpqxx and DBD::Pg. jdbc and odbc should be moved if and only if their maintainers want it. I'm not in a hurry to move the rest; they're small and don't generate a lot of CVS traffic. Note: I'm happy enough seeing ppl starting to consider moving this stuff over to GBorg, I, by no means, expect everything to go overnight, or even before v7.3 ... As I mentioned in another message, I'm also kinda hoping that if we start to divert traffic to GBorg for stuff like this, then some of the other projects might 'come alive' again as well ... ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: Removing Libraries (Was: Re: [HACKERS] Open 7.3 issues)
Marc G. Fournier wrote: Chris has made code changes to GBorg to allow for this based on requests from Dave Page (ie. PgAdminII) ... so there is no problems with that ... As for keeping them in our main CVS, the more we put over onto GBorg, the more it will get used, test, debugged, pounded and stabilized ... hell, maybe some of the 'dead projects' that are on GBorg will come alive again also if ppl are going to GBorg and find them, download them and hit the authors for fixes :) But, moving the interfaces over will at least give ppl a reason to go over and see what is there ... OK, so create gborg projects for all interfaces, and allow them to release independently. I think we have agreement on that. It can only be a win. That also gives us a mailing list and bug tracking for each interface, which is nice. I think the only unknown is whether their CVS's should be moved out of the main tree. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send unregister YourEmailAddressHere to [EMAIL PROTECTED])
Re: Removing Libraries (Was: Re: [HACKERS] Open 7.3 issues)
On Sat, 17 Aug 2002, Bruce Momjian wrote: Marc G. Fournier wrote: Chris has made code changes to GBorg to allow for this based on requests from Dave Page (ie. PgAdminII) ... so there is no problems with that ... As for keeping them in our main CVS, the more we put over onto GBorg, the more it will get used, test, debugged, pounded and stabilized ... hell, maybe some of the 'dead projects' that are on GBorg will come alive again also if ppl are going to GBorg and find them, download them and hit the authors for fixes :) But, moving the interfaces over will at least give ppl a reason to go over and see what is there ... OK, so create gborg projects for all interfaces, and allow them to release independently. I think we have agreement on that. It can only be a win. That also gives us a mailing list and bug tracking for each interface, which is nice. I think the only unknown is whether their CVS's should be moved out of the main tree. Yes, they should be ... maintaining sources in two places would be 'nightmarish' *and* at least GBorg will give a maintainer the ability to add other developers to have CVS access as well, or transferrign maintainership over to someone else ... GBorg is setup so that each project has its own CVSROOT, and its own access controls ... ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
Re: Removing Libraries (Was: Re: [HACKERS] Open 7.3 issues)
Marc G. Fournier [EMAIL PROTECTED] writes: I think the only unknown is whether their CVS's should be moved out of the main tree. Yes, they should be ... Certainly. I was a bit worried about losing CVS history, but Marc indicated he could make the move with history and all, so there's no downside. regards, tom lane ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: Removing Libraries (Was: Re: [HACKERS] Open 7.3 issues)
On Sat, 17 Aug 2002, Tom Lane wrote: Marc G. Fournier [EMAIL PROTECTED] writes: I think the only unknown is whether their CVS's should be moved out of the main tree. Yes, they should be ... Certainly. I was a bit worried about losing CVS history, but Marc indicated he could make the move with history and all, so there's no downside. Okay, here is what I'd like to suggest ... Bruce, let's start off really simple ... go create a project for libpq++ (I believe someone even volunteered to maintain it?) and let me know once created, and I'll move the CVS directory over for libpq++ and out of the pgsql-server directory ... ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
