Dear Julian,
After discussion with Vadim today, we are more than welcome to compile the
RPMs for wxWindows and deliver them to you. At pgAdmin project, we need
official binary RPMs to enter the main distributions.
I will try a dry run of your spec file under RedHat, Mandrake and SuSE
tonight. The persons with potential interest in rebuilding wxGTK2.5 official
binaries/packages are:
- Hiroshi Saito <saito@inetrt.skcapi.co.jp> (FreeBSD)
- Dave Page <dpage@vale-housing.co.uk> (Slackware)
- Raphaël Enrici <blacknoz@club-internet.fr> (Debian)
- Andreas Pflug <pgadmin@pse-consulting.de> (Win32)
We need to coordinate and will get back to you shortly.
Cheers,
Jean-Michel
> Hi Jean-Michel,
>
> Many thanks for your offer to make RPMs! This will
> save us a lot of pain.
>
> You may have talked to Vadim already so the following
> may be redundant. We think our .spec files are pretty
> much OK, and they're in the top-level wxWindows CVS
> directory: wxGTK.spec, wxX11.spec, wxMotif.spec,
> wxBase.spec. wxWINE.spec can be ignored for now, it's
> not up-to-date anyway.
>
> Our instructions for creating RPMs are in docs/tech/tn0013.txt.
>
> At 13:46 15/09/2003 +0200, Jean-Michel POURE wrote:
> >To release official RPMs fast, the workflow can be as follows:
> >- you design the RPM specs with the required options.
> >- we build the RPMs and SRPMs everyday from CVS
>
> Cool. Perhaps we can edit a file in CVS that lists
> the tags we require RPMs to be built from? That way
> when we tag a new version, we can update the file
> and just wait for the tarballs and RPMs to be generated.
> This would be a very nice way of doing the Linux releases.
>
> I suggest we create a file
>
> distrib/linux/releases.txt
>
> with one line per spin, and fields for:
>
> tag, .spec file, archive name, flags to pass to RPM
> (or e.g. NORPM for no RPM, just tarball). Archive name may
> not be appropriate if specified by the .spec file but somehow
> we're going to have to differentiate the various builds (e.g.
> Unicode/ANSI, GTK+1/GTK+2).
>
> We could maybe create or reuse a mailing list for sending
> spin reports to.
>
> >and upload them to our central package server snake.pgadmin.org.
> >- you download the packages and upload them to SourceForge.
>
> Sounds good!
>
> Many thanks,
>
> Julian
> =========================================================================
> Julian Smart mailto:julian.smart@btopenworld.com
> 3 Water Street, Stamford, www.anthemion.co.uk
> Lincs, U.K., PE9 2NJ +44 (0)1780 765976
> StoryLines: story structuring www.storylinescentral.com
> HelpBlocks: HTML help authoring www.helpblocks.com
> DialogBlocks: cross-platform dialogs www.anthemion.co.uk/dialogblocks
> =========================================================================
