mirror of https://github.com/GNOME/gimp.git
8d8c77730c
Update in particular the tarball creation steps. We now use tarballs generated by the CI. I still leave information for doing it locally in this howto, but mostly so that we can easily find this info for testing or fixing dist bugs when needed. Other than this, if the CI works flawlessly, a successful pipeline ends up with a proper tarball. The main advantages of this approach are: - Transparency: the full distribution process is now fully accessible on Gitlab, from the source, through the build (including all the logs) and up to the final tarball. Even the checksums are generated by the CI, making it easy to recognize if different tarballs were published on the download website or mirrors. This makes for a much safer and trustworthy publication process. - Less bus factor: we don't rely as much on a single person to take care of the whole process. - More automatization: a release still has to be prepared and verified manually (it always will), but at least the whole tarball creation is now automated. The next step will be to automate also the publication on the download server. |
||
---|---|---|
.gitlab | ||
app | ||
app-tools | ||
build | ||
cursors | ||
data | ||
desktop | ||
devel-docs | ||
docs | ||
etc | ||
extensions | ||
icons | ||
libgimp | ||
libgimpbase | ||
libgimpcolor | ||
libgimpconfig | ||
libgimpmath | ||
libgimpmodule | ||
libgimpthumb | ||
libgimpwidgets | ||
m4macros | ||
menus | ||
modules | ||
pdb | ||
plug-ins | ||
po | ||
po-libgimp | ||
po-plug-ins | ||
po-python | ||
po-script-fu | ||
po-tags | ||
po-tips | ||
po-windows-installer | ||
themes | ||
tools | ||
.dir-locals.el | ||
.gitignore | ||
.gitlab-ci.yml | ||
.kateconfig | ||
AUTHORS | ||
COPYING | ||
ChangeLog.pre-1-0 | ||
ChangeLog.pre-1-2 | ||
ChangeLog.pre-2-0 | ||
ChangeLog.pre-2-2 | ||
ChangeLog.pre-2-4 | ||
ChangeLog.pre-2-6 | ||
ChangeLog.pre-git | ||
HACKING | ||
INSTALL.in | ||
LICENSE | ||
MAINTAINERS | ||
Makefile.am | ||
NEWS | ||
NEWS.pre-2-0 | ||
NEWS.pre-2-2 | ||
NEWS.pre-2-4 | ||
NEWS.pre-2-6 | ||
NEWS.pre-2-8 | ||
NEWS.pre-2-10 | ||
README | ||
README.i18n | ||
acinclude.m4 | ||
authors.dtd | ||
authors.xml | ||
authors.xsl | ||
authors4gimp-web.xsl | ||
autogen.sh | ||
config.h.win32 | ||
configure.ac | ||
gimp-zip.in | ||
gimp.doap | ||
gimp.pc.in | ||
gimpthumb.pc.in | ||
gimpui.pc.in | ||
meson.build | ||
meson.make | ||
meson_dist_script.sh | ||
meson_options.txt |
README
------------------------------ GNU Image Manipulation Program 2.99 Development Branch ------------------------------ This is an unstable development release, an intermediate state on the way to the next stable release: GIMP 3. GIMP 2.99 may or may not do what you expect. Save your work early and often. If you want a stable version, please use GIMP 2.10 instead. If you think you found a bug in this version, please make sure that it hasn't been reported earlier and that it is not just new stuff that is still being worked on and obviously not quite finished yet. If you want to hack on GIMP, please read the file HACKING. For detailed installation instructions, see the file INSTALL. 1. Web Resources ================ GIMP's home page is at: https://www.gimp.org/ Please be sure to visit this site for information, documentation, tutorials, news, etc. All things GIMP-ish are available from there. There you can get the latest versions of plug-ins, using a convenient forms-based interface. The latest version of GIMP can be found at: https://www.gimp.org/downloads/ 2. Mailing Lists ================ We have several mailing lists dedicated to GIMP user and development discussion. There is more info at https://www.gimp.org/mail_lists.html Links to several archives of the mailing lists are included in that page. Gimp-user-list is a mailing list dedicated to user problems, hints and tips, discussion of cool effects, etc. Gimp-developer-list is oriented to GIMP core and plug-in developers. Gimp-gui-list is for discussing about GIMP interface to improve user experience. Most people will only want to be subscribed to gimp-user-list. If you want to help develop GIMP, the gimp-developer mailing list is a good starting point; if you want to help with GUI design, the gimp-gui list is where you want to subscribe. 3. IRC ====== And finally, for the real junkies, there is an IRC channel devoted to GIMP. On GIMPNet (a private free software oriented network) there is #gimp. Many of the developers hang out there. Some of the GIMPNet servers are: irc.gimp.org:6667 irc.us.gimp.org:6667 irc.eu.gimp.org:6667 4. Customizing ============== The look of GIMP's interface can be customized like any other GTK+ app by editing files in `${XDG_CONFIG_HOME}/gtk-3.0/` (settings.ini and gtk.css in particular) or by using "themes" (ready-made customizations). Additionally, GIMP reads `${XDG_CONFIG_HOME}/GIMP/2.99/gimp.css` so you can have settings that only apply to GIMP. Included is a set of keybindings similar to those in Adobe Photoshop. You can find them in the ps-menurc file. To use them, copy this file to `${XDG_CONFIG_HOME}/GIMP/2.99/menurc`. You can also manually change the keybindings to any of your choice by editing: `${XDG_CONFIG_HOME}/GIMP/2.99/menurc`. Have fun, Spencer Kimball Peter Mattis Federico Mena Manish Singh Sven Neumann Michael Natterer Dave Neary Martin Nordholts Jehan