pginstaller - pginst: Update JDBC to build 7.4.215.
Log Message:
-----------
Update JDBC to build 7.4.215.
Modified Files:
--------------
pginst/wxs:
pginst.wxs (r1.44 -> r1.45)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pginstaller/pginst/wxs/pginst.wxs.diff?r1=1.44&r2=1.45)
On Wed, 8 Sep 2004, User Dpage wrote:
Log Message:
-----------
Update JDBC to build 7.4.215.
If this is for the 8.0 release you should be using the 8.0 drivers
(pgdev.305, these could perhaps be named better.)
Also I don't know if/how your installer is setup to do upgrades. Does
a file like pg74.215.jdbc3.jar get renamed to a generic file like
pg74.jdbc3.jar so that an upgrade can overwrite that file so that an
application referencing the file automatically picks up new changes?
Kris Jurka
Kris Jurka wrote:
On Wed, 8 Sep 2004, User Dpage wrote:
Log Message:
-----------
Update JDBC to build 7.4.215.If this is for the 8.0 release you should be using the 8.0 drivers
(pgdev.305, these could perhaps be named better.)Also I don't know if/how your installer is setup to do upgrades.
Does a file like pg74.215.jdbc3.jar get renamed to a generic file
like pg74.jdbc3.jar so that an upgrade can overwrite that file so
that an application referencing the file automatically picks up new
changes?
This is a good example why dumping all commit messages from pgfoundry
onto one list is bad. How can I filter out these reponses?
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
On Mon, 13 Sep 2004, Peter Eisentraut wrote:
Kris Jurka wrote:
On Wed, 8 Sep 2004, User Dpage wrote:
Log Message:
-----------
Update JDBC to build 7.4.215.If this is for the 8.0 release you should be using the 8.0 drivers
(pgdev.305, these could perhaps be named better.)Also I don't know if/how your installer is setup to do upgrades.
Does a file like pg74.215.jdbc3.jar get renamed to a generic file
like pg74.jdbc3.jar so that an upgrade can overwrite that file so
that an application referencing the file automatically picks up new
changes?This is a good example why dumping all commit messages from pgfoundry
onto one list is bad. How can I filter out these reponses?
get rid of everything with either a To or From being @pgfoundry.org
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
On Mon, 13 Sep 2004, Peter Eisentraut wrote:
This is a good example why dumping all commit messages from pgfoundry
onto one list is bad. How can I filter out these reponses?
At first I was about to recant my condemnation of this "feature" when I
replied to the message, but it's yet to prove its usefulness and pgfoundry
really hasn't taken off yet to overwhelm us with it's volume.
I read this message and wanted to reply to someone associated with the
installer, unfortunately I can't. The from address (dpage@pgfoundry.org)
bounces and the committers list isn't who I want to address. There's no
association with the installer project other than the subject.
Kris Jurka
Kris Jurka <books@ejurka.com> writes:
I read this message and wanted to reply to someone associated with the
installer, unfortunately I can't. The from address (dpage@pgfoundry.org)
bounces and the committers list isn't who I want to address.
That's been a problem all along with commit messages from the core
project as well. The From: address emitted by cvs log doesn't have much
of anything to do with the committer's actual email address. I dunno
how fixable this is, but it'd sure be nice if it could be fixed.
regards, tom lane
Tom Lane wrote:
Kris Jurka <books@ejurka.com> writes:
I read this message and wanted to reply to someone associated with the
installer, unfortunately I can't. The from address (dpage@pgfoundry.org)
bounces and the committers list isn't who I want to address.That's been a problem all along with commit messages from the core
project as well. The From: address emitted by cvs log doesn't have much
of anything to do with the committer's actual email address. I dunno
how fixable this is, but it'd sure be nice if it could be fixed.
I wonder if we should just have the "from" be the committers list and
don't even try to get the user name.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073On Mon, 13 Sep 2004, Bruce Momjian wrote:
Tom Lane wrote:
Kris Jurka <books@ejurka.com> writes:
I read this message and wanted to reply to someone associated with the
installer, unfortunately I can't. The from address (dpage@pgfoundry.org)
bounces and the committers list isn't who I want to address.That's been a problem all along with commit messages from the core
project as well. The From: address emitted by cvs log doesn't have much
of anything to do with the committer's actual email address. I dunno
how fixable this is, but it'd sure be nice if it could be fixed.I wonder if we should just have the "from" be the committers list and
don't even try to get the user name.
The former is impossible, as far as I know ... but the later is doable if
that is what ppl would like to see ...
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: scrappy@hub.org Yahoo!: yscrappy ICQ: 7615664
"Marc G. Fournier" <scrappy@postgresql.org> writes:
On Mon, 13 Sep 2004, Bruce Momjian wrote:
I wonder if we should just have the "from" be the committers list and
don't even try to get the user name.
The former is impossible, as far as I know ... but the later is doable if
that is what ppl would like to see ...
No, definitely not. The way it is, at least I can see who made the
commit, even if it takes some work to reply to them ...
regards, tom lane