On Wed, 15 Nov 2006 10:15:18 +0100 Thomas Kuther <[EMAIL PROTECTED]> babbled:
> On Wed, 15 Nov 2006 09:57:59 +0100 > John Kraal <[EMAIL PROTECTED]> wrote: > > > Thomas Kuther wrote: > > > On Wed, 15 Nov 2006 14:28:54 +1100 > > > Metrics <[EMAIL PROTECTED]> wrote: > > > > > >> On Wed, Nov 15, 2006 at 01:41:57PM +1100, Daniel Kasak wrote: > > >>> For around a week or more now, the 'Restart' menu item has been > > >>> shutting down Enlightenment-0.17 for me instead of restarting it. > > >>> > > >>> -- > > >>> Daniel Kasak > > >>> IT Developer > > >>> NUS Consulting Group > > >>> Level 5, 77 Pacific Highway > > >>> North Sydney, NSW, Australia 2060 > > >>> T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 > > >>> email: [EMAIL PROTECTED] > > >>> website: http://www.nusconsulting.com.au > > >>> > > >> The cause is most probably due to the fact that the enlightenment > > >> binary in your install is not called "enlightenment". On gentoo > > >> it's something like "enlightenment-0.17" or something. Symlink > > >> will fix it. > > >> > > >> metrics > > >> > > > > > > seconded! > > > works on my vector laptop where the binary is called > > > "enlightenment", and fails on the gentoo box, where the ebuild > > > installs it as "enlightenment-0.17". > > > The e ebuild needs a fix, as e16 installs as "e16" anyway. Just > > > older versions of e16 would be affected. > > > Currently the ebuild does an ugly hack and seds enlightenment --> > > > enlightenment-0.17 in e_start_main.c > > > > > > Regards, > > > Tom > > > > > > > > > > On Gentoo it configures enlightenment with the binary-executable-name > > thingy a little different, the right option should be - imo - that the > > restart option uses that configuration-setting, propably from config.h > > > > not fully true: > from /usr/portage/x11-wm/e/e-9999.ebuild > > -----8<------ > src_unpack() { > enlightenment_src_unpack > sed -i \ > -e 's:bin/enlightenment:bin/enlightenment-0.17:' \ > "${S}"/src/bin/e_start_main.c || die > } > > src_install() { > enlightenment_src_install > mv "${D}"/usr/bin/enlightenment{,-0.17} > } > ----->8---- > > and enlightenment.eclass doesn't say anything about > binary-executeable-name. > It's just a hack in the ebuild, nothing else. > > Regards, > Tom e17 uses its argv[0] and re-executes that. the ebuild is a hack that happens to be incomplete for e17. :) e17 is working to replace e16 thus we are not renaming our executable "upstream" :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
