Uploading binaries to ftp.gnome.org

First, similar concerns to source code releases apply here: See MaintainersCorner/Releasing.

We need to document what source code was used, and how to compile it. This will be implemented by adding a file called SOURCES in each directory that contains binary files. The SOURCES file describes how to generate those binaries. If you have independent binaries, at present, we recommend using separate directories.

SOURCES file example

 Source: http://git.gnome.org/browse/tomboy/tag/?id=1.7.7

 See these two pages for instructions on building this binary:
  https://live.gnome.org/Tomboy/ReleaseChecklist
  https://live.gnome.org/Tomboy/Building/Windows

 This binary was generated with Visual Studio 2008 on Windows 7,
 using gtk-sharp-sdk-2.12.7.

Uploading binaries

If you provide binaries of your package (e.g. for Windows), then scp these to master.gnome.org, placing them into e.g. /ftp/pub/GNOME/binaries/win32/gnome-panel/2.3/. You will need to create a directory for your project if there isn’t one already. Also make sure to add contact information into /ftp/pub/GNOME/binaries/win32/README in this case. Finally, make sure to add a SOURCES file detailing how to build the binaries. When you are done, run signal-ftp-sync on master.gnome.org.

MaintainersCorner/Binaries (last edited 2022-08-08 20:59:59 by SébastienWilmet)