On Thu, 26 Feb 2009, Sebastian Pipping wrote: > First thanks for your quick and friendly reply. > > Sorry for the things I should have done better, > like sending the mail to cc-de before by mistake. > It seems in moderation - anybody got the power to stop it?
It seems to be already taken care of. No big deal. > Asheesh Laroia wrote: >> On Thu, 26 Feb 2009, Sebastian Pipping wrote: >> >>> A few comments and questions: >>> >>> - liblicense-0.8.1 gives a link error for me, though configure >>> went through all fine: >>> ../liblicense/.libs/liblicense.so: undefined reference to `dlsym' >>> ../liblicense/.libs/liblicense.so: undefined reference to `dlerror' >>> ../liblicense/.libs/liblicense.so: undefined reference to `dlopen' >>> ../liblicense/.libs/liblicense.so: undefined reference to `dlclose' >>> A -ldl is missing in utils/Makefile.am >> >> Thanks. I just committed and pushed a probable fix. Does that do it for >> you? > > On [1] it reads: > > "[LDADD] is used to specify additional objects or libraries to link > with; it is inappropriate for specifying specific linker flags, you > should use AM_LDFLAGS for this purpose." > > Attached is a little patch to improve on that. > > [1] http://www.gnu.org/software/hello/manual/automake/Linking.html Thanks. I wasn't really sure that the way I did it was right; I was hoping you would check me, which you did. Thanks! (Your patch is applied and pushed.) > > >>> - Why is the "licenses" folder empty in the liblicense git repo? >>> This makes autoconf fail from ./autogen.sh >>> >>> - The "Developers: Using git" [3] section lists the command >>> git submodule init >>> git submodule update >>> I think the page should explain why that is needed. >> >> These two issues are related; doing the "git submodule init ; git >> submodule update" fills out the licenses directory. (It's like >> svn:externals.) Once you see what I mean, would you be willing to >> improve the wiki page to explain this? > > I created a wiki account but my permission do not suffice. > Great to find out Git can do externals. You just have to confirm your email address and you can edit to your heart's content. >>> - Whom could I team up with when creating an I/O module >>> for XSPF [2] files? >> >> What does your [2] refer to? > > Sorry: > > [2] http://xspf.org/ Yup. I'm familiar with XSPF, at least in the broadest strokes. >> Regardless, I'd be the person to talk to, but hopefully you can do a lot >> of the work! > > :-) > > >>> - How can I get emblems auto-detected emblems like this?: >>> http://wiki.creativecommons.org/Image:Ll_nautilus_emblem.png >>> It seems installing liblicense-0.8.1 is not enough? >> >> Yeah - it relates to a module called liblicense-gnome that we've been >> doing a poor job of maintaining due to really spread-out developer >> resources. It lives in svn at >> http://code.creativecommons.org/svnroot/liblicense-gnome/. > > I gave liblicense-gnome-0.4 a try. Emblem icons are now available > but licensing dialogs seem missing. Are they in there, too? Licensing dialogs, let me see... That's gui_gtk.py. It's exposed in a file's properties pane in Nautilus, assuming the code still works, as per nautilus-liblicense.py, which you should have to squeeze into the Nautilus Python extensions directory. Keep the questions coming! -- Asheesh. -- Q: How many psychiatrists does it take to change a light bulb? A: Only one, but it takes a long time, and the light bulb has to really want to change. _______________________________________________ cc-devel mailing list [email protected] http://lists.ibiblio.org/mailman/listinfo/cc-devel
