I attach a new, updated ebuild. Biggest changes are: - new warnings in pkg_postinst - new econf, this version will use portage CFLAGS... - new DEPEND, I forgot fbset in prev versions - other clean ups
Created attachment 23510 [details] ebuild for qingy 0.3.0
Created attachment 24192 [details] qingy-0.3.0.ebuild I've modified your ebuild to correct a few things: - the compile time use of "fbset" breaks in userpriv mode (see bug #38863) => I've removed this from makefile, and instead I install the creatercfile and ask the user to call the pkg_config() function. As a side effect, I've removed fbset from DEPEND and put it in REDEPEND (I've assumed that pkg_config was more runtime than compile time, but I may be wrong). - the themes images and fonts in /etc are imo a very bad idea. They breaks etc-update and dispatch-conf, and are against the FHS. I've moved them to /usr/share, and symlinked from /etc (I had to use this symlink because the code assumes that config and data are in the same dir). The old themes dir, if any, is moved at preinst time, otherwise it would not have been overwritten by the symlink. There may be other small cosmetic changes also, but nothing important. What do you think of this version, is it ok for you? I've also wondered if it would be a good idea to make pkg_config apply the changes needed to /etc/inittab, but I'm not really sure.
Created attachment 24200 [details] qingy-themepack-1.0.ebuild I thought it would be cool to also have your themepack in portage, it's more userfriendly like this. So here is a "download and unpack" ebuild. I still wonder two things though: - in what category can this fall? "x11-themes" is probably the most close one, but, well, it's not x11... - under which license this can be released? I see there are several fonts inside, and I know fonts always uses very specific licenses... Or maybe you've checked this already?
The new ebuild for qingy looks good to me... Now that you make me thing about it, /usr/share/qingy/themes looks like a good place, expect them in there by default for next version ;-P As for pkg_config(), I would like the creation of config file to be a transparent process for the user... maybe I'll search for a better way to handle that (not that I didn't search before, though :-/ ). Anyway, this change is OK to me, only let's warn the user about it in pkg_postinst()... About the themepack ebuild, yes, "x11-themes" looks like the nearest cathegory, at least a generic "app-themes" springs out from the void... As for the licenses, some themes I got from gentoo-forums, others from friends of mine, and they can all be considered GPL (or is it LGPL for works of art?). But concerning fonts, let me see: there comes the default that comes with DirectFB and that is OK, there is Vera (ttf-bitstream-vera in portage), and courdb and lucida that I believe are from M$ (but are included by the xfree ebuild if truetype flag is set, if I'm not mistaken)... Sorry I can't help you more then this right now, I'll dig deeper as soon as I have a little more time.
Could you merge qingy ebuild into portage? You know, version 0.4.0 is already on its way ;-P In version 0.4.0, according to input from this bug, I changed the install locations according to the FHS, and devised some code to detect FB resolution at run time. Thus there will no more need of fbset. About the themepack ebuild, I plan to open a qingy themes section on FreshMeat, and move there the themes now hosted on qingy SF page. Thus this themepack ebuild would be unusable in the (near) future.
just added 0.3.0 some minutes ago, with the ebuild of your sf site.
