:) (is my english so bad ? ;p )Dear Raphaël, So you are the second French guy around...
Nice to hear from you. We really appreciate your help. As Dave already answered, you can start with the unix_compilation.html page in CVS. I updated it today to remember to add a simlink, otherwise compilation will fail.Ok... In a first time I didn't find these pages because I was working on the 20030613 snapshots. I think these pages were not included. It's now corrected in latest snapshots. (Hey Dave, I've bought some soap! :p [private joke]).
Maybe you should also have a look at the wxGTK2ud.spec and pgadmin3.spec files which areat the top of the CVS root. It gives the list of the required files to install. Also, I chose the wxGTK2ud-2.5-dateoftheday for the wxGTK 2.5 packages, but you may have other naming conventions at Debian...I'll check this... In fact everything seems to be well prepared in wxWindows cvs snapshots to get a working debian package but I can't get it compile right for the moment (I'm going to contact the debian packager of wxWindows to ask him what would be the better way to get a 2.5 version without breaking his work).
When you are finished, how do you plan to distribute the package? Because pgAdmin3 is under heavy development, it sometimes needs a daily build to keep track of evolutions and bug fixes. Do you plan to upload daily packages to snake.pgadmin.org? Or do you plan to use Debian repositories?I think that, when my packaging work will be quite stable, it would be nice to integrate the debian's packaging files in the pgadmin3 CVS so that it can be automatically generated (how are you doing concerning the RH RPMS, Suse RPMS and MDK rpms ?). I think it's too early for the moment to plan to use the debian repositories and that it would be better to upload everything on snake in a first time.
Also, it would be nice to describe the needed steps for compilation in snapshots.html pages in docs folder (this page was added today).I'll have a look at this.
The principal problems I encountered were the pgsql includes that are in /usr/include/postgresql on debian and the wxWindows 2.5 I exposed before. I solved the include problem by doing an export CPPFLAGS="-I /usr/include/postgresql" before doing the configure in the debian/rules. But It seems you are working on this.
Hope I won't be to slow for all of you guys... You seem to be really reactive! :)
Cheers,
Raphaël
---------------------------(end of broadcast)--------------------------- TIP 7: don't forget to increase your free space map settings
