On 08/23/2009 03:04 AM, Laurence J. Lane wrote:
e16 is essentially forked code and a new package based on enlightenment. e16 isn't a drop-in replacement for enlightenment 0.16x. It's actually intended to not interfere with enlightenment.
I would, in that case, have argued that the enlightenment package should not be removed until either such a replacement or an automated migration mechanism could be provided - but I can see how doing it that way could have been difficult, and in any case, what's past is done.
The configuration files are not compatible, but some of the menus are. There's a README with some notes on migrating. It's temporarily not in the e16 1.0.0-x packages, but you can see it here: http://trac.enlightenment.org/e/browser/trunk/E16/e/docs/README
Thank you for the link. Is there any chance of a notice about this change, and possibly a pointer to that file, being provided when installing e16 and having enlightenment already installed? Without something like that, I would expect that other people will trip over the change unexpectedly in much the same way I did, and not necessarily be able to revert the way I was (even for just the short term). From the description in that file, it seems as if it would be simple enough to write a "dumb" script to be run by hand to convert a given user's ~/.enlightenment to a ~/.e16 in an automated fashion; dependong on how dumb would be acceptable, I could write one myself. With a bit more smarts (e.g. a prompt to compare before replacing existing files, such as is used by apt-get when a config file has been changed), might it not be a good idea to provide such a script along with the e16 package - or perhaps in a transitional "dummy" enlightenment package? (And possibly also symlink the enlightenment executable to e16 at install time, if no file or symlink with that name already exists in the appropriate location?)
The transition you seek is actually a change from enlightenment DR 0.16 to enlightenment DR 0.17. Various people from the e17 packaging team pestered me give up the enlightenment package. I eventually abandoned it and moved to e16, but the e17 packaging team decided not to use the enlightenment package.
Okay. (For what it's worth, I actually support in principle the name 'e16' over 'enlightenment', I just don't like the lack of a migration path.) I've been interested in e17 in the past, but haven't switched for a variety of reasons, not least that it looks to be considerably heavier than e16. Should I plan to go that route, or are the changes from e16 to e17 big enough that I would be likely to prefer staying with e16 for the time being? -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
