Bug#541477: closed by Marco Rodrigues goth...@sapo.pt (Package enlightenment has been removed from Debian)
On Sat, Aug 22, 2009 at 8:03 PM, The Wandererwande...@fastmail.fm 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. 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 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. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541477: closed by Marco Rodrigues goth...@sapo.pt (Package enlightenment has been removed from Debian)
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 debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541477: closed by Marco Rodrigues goth...@sapo.pt (Package enlightenment has been removed from Debian)
On 08/22/2009 01:53 PM, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the enlightenment package: #541477: enlightenment: configuration lost in update to e16 It has been closed by Marco Rodrigues goth...@sapo.pt. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Marco Rodrigues goth...@sapo.pt by replying to this email. It is indeed unsatisfactory. You filled the bug http://bugs.debian.org/541477 in Debian BTS against the package enlightenment. I'm closing it at *unstable*, but it will remain open for older distributions. For more information about this package's removal, read http://bugs.debian.org/492508. That bug might give the reasons why this package was removed and suggestions of possible replacements. Don't hesitate to reply to this mail if you have any question. As it happens, I had found that particular bug report myself in the last few days. It does not seem to provide the reasons for the package being removed (it simply states that that is the case), and the possible replacement which it indirectly suggests - e16 - is not viable, for the reasons I gave in my own bug report and which I elaborate on below. I am aware that the enlightenment package has been removed from Debian; that is precisely the problem, or at least part of it. According to the bug report you linked to, the enlightenment package has been replaced by the e16 package; however, according to what I have been told in response to my own bug report, there is no upgrade path from enlightenment to e16. It is therefore not viable to simply uninstall enlightenment and install e16, as I would expect to be the procedure for a replacement update; further configuration is needed. What's more, as far as I was able to tell when I inadvertently made the experiment, simply copying the ~/.enlightenment directory to ~/.e16 would not work; at a glance, the directories and the files they contain seem to have different formats. It does not appear to be possible to upgrade cleanly from enlightenment to e16 without losing configuration settings. e16 is stated to be the replacement for enlightenment (though apparently this is not advertised in ay way which would bring the fact to the attention of people who might need to make the switch). This seems to me to be a very obvious and very serious problem, which is in serious need of fixing before the removal of enlightenment can be made truly final. I understand if it is not possible (within the package guidelines) to automatically convert ~/.foobar config settings between packages, for technical and policy reasons. However, I would expect that if those settings will be lost, there would at least be a prominent alert message at install time (e.g. via apt-listchanges or simply the curses-based configuration dialogs) that these settings will have to be migrated by hand, with either an explanation of how to do so or a link to a place to find such an explanation. That would not be truly satisfactory, but it would be sufficient if no better solution is practical. Thank you for your contribution to Debian. You're quite welcome. I'd prefer to contribute more (and more practically) than I have, but I haven't had much time, and what I have has been taken up by other interests. Just because I'm less than happy in this case shouldn't be taken to mean that I'm unhappy with Debian; I like it very much, and that's precisely why it bothers me that a problem like this is being dismissed the way this one seems to be. -- The Wanderer Warning: Simply because I argue an issue does not mean I agree with any side of it. Secrecy is the beginning of tyranny. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
