Thread: pgadmin3.chm in CVS

pgadmin3.chm in CVS

From
"Dave Page"
Date:
Hi Andreas,

After a particularly painful CVS update, I have removed pgadmin3.chm
from CVS. As you know, it's a large compiled file, only useful to
Windows users, and can easily be compiled using free tools from
Microsoft. In addition of course, pgAdmin will function just fine with
the raw HTML files.

For the Win32 builds I will ensure that an recompile is done prior to
the installer build - I assume it will make no difference to you for the
snapshots as you would have built the file first anyway?

Regards, Dave

Re: pgadmin3.chm in CVS

From
Andreas Pflug
Date:
Dave Page wrote:

>Hi Andreas,
>
>After a particularly painful CVS update, I have removed pgadmin3.chm
>from CVS. As you know, it's a large compiled file, only useful to
>Windows users,
>
This will change very soon, there's a wx implementation for gtk on the way.
There are already contribs that can do it, and a patch is pending to
have it in wx2.5

IMHO, we need a download location for "misc. binaries" for *.chm and
*.mo. We don't need versions for any of them.

Regards,
Andreas



Re: pgadmin3.chm in CVS

From
"Dave Page"
Date:

> -----Original Message-----
> From: Andreas Pflug [mailto:pgadmin@pse-consulting.de]
> Sent: 09 September 2003 21:14
> To: Dave Page
> Cc: pgadmin-hackers
> Subject: Re: [pgadmin-hackers] pgadmin3.chm in CVS
>
>
> Dave Page wrote:
>
> >Hi Andreas,
> >
> >After a particularly painful CVS update, I have removed pgadmin3.chm
> >from CVS. As you know, it's a large compiled file, only useful to
> >Windows users,
> >
> This will change very soon, there's a wx implementation for
> gtk on the way. There are already contribs that can do it,
> and a patch is pending to
> have it in wx2.5
>
> IMHO, we need a download location for "misc. binaries" for *.chm and
> *.mo. We don't need versions for any of them.

I have no problem with that at all - please feel free to create
something in the snapshots or ftp areas, or let me know what you want
and I'll do it.

For the .mo files however, I think there are valid reasons to keep them
in CVS:

1) They are very small.
2) They are needed by all builds and distributions.
3) There is no simple method to compile them as part of the build
process (particularly on Windows). (Yes, I know this point is arguable).

Regards, Dave.