Guess what…
… I’ve new “fun” with release-management. This time “make distcheck”, which was recommended to me, is bocking my work.
The amount of work that is needed to “ship a line of code” to users is insane.
… I’ve new “fun” with release-management. This time “make distcheck”, which was recommended to me, is bocking my work.
The amount of work that is needed to “ship a line of code” to users is insane.
July 20th, 2009 at 4:57 pm
downer…. you must have been pretty chuffed when the new gdm made it through though.
July 20th, 2009 at 5:01 pm
Give us details so that we can help you.
July 20th, 2009 at 5:13 pm
@ tretle: I’ve no clue what \chuffed\ means.
@ Jason: Easy… bzr branch lp:notify-osd ; cd notify-osd ; autoreconf ; ./autogen.sh ; make distcheck (and then I was surprised by the output)
July 20th, 2009 at 7:15 pm
lolz, it means happy or pleased… And I remember correctly you were waiting for the new gdm to hit for awhile.
July 20th, 2009 at 10:02 pm
You’ll need to add the *.gcno files to the CLEANFILES in tests/ to fix the rest of it:
http://www.gnome.org/~hadess/mirco-doesnt-know-autotools.patch
FWIW:
- autotools’ distcheck uses underscores in the path, so don’t use them as separator in sed
- don’t use relative paths, always use $(top_srcdir) or $(srcdir) for source dirs
- don’t use fixed paths in destinations, use symbolic names (eg. not /usr/share but $(datadir)
And your use of sources that aren’t in the current directory should be removed, but this works…
July 24th, 2009 at 1:01 am
Nice to see that you credited me for your commit:
http://bazaar.launchpad.net/~macslow/notify-osd/make-distcheck-pain/revision/352
July 24th, 2009 at 8:31 am
@ Bastien: Not there in the scratchpad “make-distcheck-pain” branch, but in the main one http://bazaar.launchpad.net/~notify-osd-developers/notify-osd/main/revision/352 where I merged in your stuff. In these by-the-side branches I never keep track of those things, only in the main trunk were everybody can see it.