Postgres Pro
Downloads
Home   >   mailing lists

Thread: Update

Update

From
"Adam H. Pendleton"
Date:
Hello everyone!  I've been out of town for the weekend, so I wasn't able
to work on any pgAdmin stuff while I was gone.  I'm going to get back
into it, so I wanted to make sure that I've got everything on my to-do list:

*) Fix -DSSL compilation problem
*) Make static build more static
*) Fix J-M's xpm include problem
*) RH 7.3 SRPM building
*) Mac OS X port

Did I miss anything?

ahp

Re: Update

From
"Dave Page"
Date:

> -----Original Message-----
> From: Adam H. Pendleton [mailto:fmonkey@fmonkey.net]
> Sent: 06 October 2003 16:07
> To: pgadmin-hackers
> Subject: [pgadmin-hackers] Update
>
>
> Hello everyone!  I've been out of town for the weekend, so I
> wasn't able
> to work on any pgAdmin stuff while I was gone.  I'm going to get back
> into it, so I wanted to make sure that I've got everything on
> my to-do list:
>
> *) Fix -DSSL compilation problem
> *) Make static build more static
> *) Fix J-M's xpm include problem
> *) RH 7.3 SRPM building
> *) Mac OS X port
>
> Did I miss anything?

Hi Adam,

It would be cool if there were a generic mechanism we could use to write
the version number into scripts 'n' stuff at configure time. The would
certainly make my life easier with various build scripts.

Regards, Dave.

Re: Update

From
"Adam H. Pendleton"
Date:
Dave Page wrote:
It would be cool if there were a generic mechanism we could use to write
the version number into scripts 'n' stuff at configure time. The would
certainly make my life easier with various build scripts.

By "write them into scripts" what do you mean?  Can you provide an example of what you would like to see?

ahp

Re: Update

From
"Dave Page"
Date:
 
-----Original Message-----
From: Adam H. Pendleton [mailto:fmonkey@fmonkey.net]
Sent: 07 October 2003 13:37
To: Dave Page
Cc: pgadmin-hackers
Subject: Re: [pgadmin-hackers] Update

Dave Page wrote:
It would be cool if there were a generic mechanism we could use to write
the version number into scripts 'n' stuff at configure time. The would
certainly make my life easier with various build scripts.

By "write them into scripts" what do you mean?  Can you provide an example of what you would like to see?
 
Say I have some code in a script that looks like:
 
mv pgadmin3.tgz pgadmin3-${VERSION}.tgz 
 
When configure runs, it then changes that to:
 
mv pgadmin3.tgz pgadmin3-1.1.0.tgz
 
Rather than change it of course, it could take script.in and create script.
 
Regards, Dave.
 
 

Re: Update

From
"Adam H. Pendleton"
Date:
Dave Page wrote:
Say I have some code in a script that looks like:
 
mv pgadmin3.tgz pgadmin3-${VERSION}.tgz 
 
When configure runs, it then changes that to:
 
mv pgadmin3.tgz pgadmin3-1.1.0.tgz
 
Rather than change it of course, it could take script.in and create script.
 
Sure, that seems easy enough to do.  The only catch would be that configure would probably have to have the version number hard-coded into it.  Otherwise it shouldn't be a problem.  If you give me some specifics, or just a script to start with, I'll take a crack at it.

ahp

Re: Update

From
"Dave Page"
Date:
 
-----Original Message-----
From: Adam H. Pendleton [mailto:fmonkey@fmonkey.net]
Sent: 07 October 2003 13:48
To: Dave Page
Cc: pgadmin-hackers
Subject: Re: [pgadmin-hackers] Update

Dave Page wrote:
Say I have some code in a script that looks like:
 
mv pgadmin3.tgz pgadmin3-${VERSION}.tgz 
 
When configure runs, it then changes that to:
 
mv pgadmin3.tgz pgadmin3-1.1.0.tgz
 
Rather than change it of course, it could take script.in and create script.
 
Sure, that seems easy enough to do.  The only catch would be that configure would probably have to have the version number hard-coded into it.  Otherwise it shouldn't be a problem.  If you give me some specifics, or just a script to start with, I'll take a crack at it.

 
I don't have a script yet as it would mean rewriting/splitting some of them - for example the pkg/src/build-tarball script would have to be split into pre and post configure sections. 
 
Can't configure get the version number from configure.ac?
 
Regards, Dave.

Re: Update

From
Andreas Pflug
Date:
Adam H. Pendleton wrote:

> Dave Page wrote:
>
>> Say I have some code in a script that looks like:
>>
>> mv pgadmin3.tgz pgadmin3-${VERSION}.tgz
>>
>> When configure runs, it then changes that to:
>>
>> mv pgadmin3.tgz pgadmin3-1.1.0.tgz
>>
>> Rather than change it of course, it could take /script.in/ and create
>> /script/.
>>
>
> Sure, that seems easy enough to do.  The only catch would be that
> configure would probably have to have the version number hard-coded
> into it.


Can't we have this grep/awk-ed from version.h? I just introduced the
macro VERSION_PACKAGE:

grep VERSION_PACKAGE src/include/version.h | awk '{print $3}'


Regards,
Andreas