Re: [Gimp-developer] why do I need babl to UNINSTALL gimp?
Owen wrote: > Well, looking at the my Makefile (recent git build, line 873) it reads; > uninstall: uninstall-recursive > > Which doesn't seem to go anywhere. Just another mystery for me > The uninstall-recursive target is enumerated in the RECURSIVE_TARGETS variable. All recursive targets are defined in one place, look for $(RECURSIVE_TARGETS):. It basically calls subdirs and invokes the uninstall-am target, which is defined as uninstall-am: uninstall-binSCRIPTS uninstall-pkgconfigDATA. HTH - Martin ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP & git - example workflows from some of our longer-term git users?
On Sat, 2009-04-25 at 17:17 +0200, Ruben Vermeersch wrote: > On Thu, 2009-04-23 at 13:34 +0200, Nils Philippsen wrote: > > On Wed, 2009-04-22 at 12:03 +0200, Michael Schumacher wrote: > > > > Von: Nils Philippsen > > > > > > > On Mon, 2009-04-20 at 19:56 +0200, Martin Nordholts wrote: > > > > > I don't think there is a need to reiterate a how-to on this mailing > > > > > list > > > > > for how to work with git. It should be quite enough to read: > > > > > http://live.gnome.org/Git/Developers > > > > > > > > > > and other git resources on the web. GIMP will not have a > > > > > super-special > > > > > workflow with regards to git. In fact, there is no workflow set in > > > > > stone > > > > > yet, we will have to experiment to wee what works and what doesn't. > > > > > > > > Just a caveat since this isn't mentioned on the web page: Rebasing > > > > changes on a branch modifies history, so don't rebase changes that are > > > > publicly visible. Use rebasing only for your private changes which you > > > > haven't pushed yet. > > > > > > See, it's things like that that I would like to see mentioned more > > > frequently and accompanied by the actual git commands (if possible). > > > > So where do you want it documented, I'll gladly write this up (with > > actual commands). > > Let's keep it all in one place: http://live.gnome.org/Git and subpages > are where this kind of stuff belongs. Okay, let's hope I can get something done until mid next week, I'll be on vacation from then on for 3 weeks and will likely have low to no net access. Nils -- Nils Philippsen / Wilhelmstraße 22 / D-71229 Leonberg n...@tiptoe.de / n...@redhat.com PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011 Ever noticed that common sense isn't really all that common? ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] why do I need babl to UNINSTALL gimp?
> Owen wrote: >>> Hi, >>> >>> I just wanted to clean out multiple gimp installations and went to >>> uninstall a gimp cvs build. >>> >>> make uninstall >> >> >> >> I am not that good at reading Makefiles, but I don't think uninstall >> does anything and you are just doing a make? >> >> Hence the requirement for a newer babl >> > > Thanks Owen, that would explain the error but I thought make reported > something like "no rule for target uninstall" if it got fed crap. > > maybe there's some default target in the gimp Makefiles that matches a > non existent target. :? Well, looking at the my Makefile (recent git build, line 873) it reads; uninstall: uninstall-recursive Which doesn't seem to go anywhere. Just another mystery for me -- Owen ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] why do I need babl to UNINSTALL gimp?
Owen wrote: >> Hi, >> >> I just wanted to clean out multiple gimp installations and went to >> uninstall a gimp cvs build. >> >> make uninstall > > > > I am not that good at reading Makefiles, but I don't think uninstall > does anything and you are just doing a make? > > Hence the requirement for a newer babl > Thanks Owen, that would explain the error but I thought make reported something like "no rule for target uninstall" if it got fed crap. maybe there's some default target in the gimp Makefiles that matches a non existent target. :? ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] why do I need babl to UNINSTALL gimp?
> Hi, > > I just wanted to clean out multiple gimp installations and went to > uninstall a gimp cvs build. > > make uninstall I am not that good at reading Makefiles, but I don't think uninstall does anything and you are just doing a make? Hence the requirement for a newer babl -- Owen ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
[Gimp-developer] why do I need babl to UNINSTALL gimp?
Hi, I just wanted to clean out multiple gimp installations and went to uninstall a gimp cvs build. make uninstall checking for gmsgfmt... (cached) /usr/bin/gmsgfmt checking for xgettext... (cached) /usr/bin/xgettext checking for iso-codes... yes checking for BABL... configure: error: Package requirements (babl >= 0.0.23) were not met: Requested 'babl >= 0.0.23' but version of babl is 0.0.22 Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables BABL_CFLAGS and BABL_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. make: *** [config.status] Error 1 Do I really need to pull babl , build and install it just to UNINSTALL Gimp ?? TIA. ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP & git - example workflows from some of our longer-term git users?
On Thu, 2009-04-23 at 13:34 +0200, Nils Philippsen wrote: > On Wed, 2009-04-22 at 12:03 +0200, Michael Schumacher wrote: > > > Von: Nils Philippsen > > > > > On Mon, 2009-04-20 at 19:56 +0200, Martin Nordholts wrote: > > > > I don't think there is a need to reiterate a how-to on this mailing list > > > > for how to work with git. It should be quite enough to read: > > > > http://live.gnome.org/Git/Developers > > > > > > > > and other git resources on the web. GIMP will not have a super-special > > > > workflow with regards to git. In fact, there is no workflow set in stone > > > > yet, we will have to experiment to wee what works and what doesn't. > > > > > > Just a caveat since this isn't mentioned on the web page: Rebasing > > > changes on a branch modifies history, so don't rebase changes that are > > > publicly visible. Use rebasing only for your private changes which you > > > haven't pushed yet. > > > > See, it's things like that that I would like to see mentioned more > > frequently and accompanied by the actual git commands (if possible). > > So where do you want it documented, I'll gladly write this up (with > actual commands). Let's keep it all in one place: http://live.gnome.org/Git and subpages are where this kind of stuff belongs. Cheers, Ruben -- Ruben Vermeersch (rubenv) http://www.savanne.be/ ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Background color property for GIMP images
Peter (yahvuu) wrote: > there's one solution i haven't seen yet: > > assign a background color to GIMP images. Not a layer, just a single > color. > This way, the eraser can always work on alpha, and all layers > consistently can have an alpha channel. I like the innovative nature of the idea. but, I am not sure about how general purpose this idea is. - I would like to see some more thinking on how this influences the simplest case: importing an image without any transparency. how would that look like without introducing complication. simple things (in users' eyes) have to remain simple in the UI. - I would like to see some more thinking on how this is related to the background color in the color chooser. coupled/decoupled? --ps founder + principal interaction architect man + machine interface works http://mmiworks.net/blog : on interaction architecture ___ Gimp-developer mailing list Gimp-developer@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer
