On Fri, Jun 5, 2009 at 5:48 AM, Matthias Saou <th...@spam.spam.spam.spam.spam.spam.spam.egg.and.spam.freshrpms.net> wrote: > Olivier Tilloy wrote : > >> This release is intended to be what we usually call a "light release": >> the update process goes through eggs in the plugin repository. The >> process is lighter for end users who just have to restart Moovida once >> all the updates are installed, and easier for us as we don't have to >> bother generating new tarballs and ubuntu packages. > > I guess this update procedure makes sense for Windows users, where > there is no real notion of a centralized networked package management > system. But for GNU/Linux distribution users, I really think the full > tarballs make more sense. > > My main concern is that right now Fedora users are going to download > 10MB of packages to install the 1.0.1 release, and that right after > running it, they'll be prompted to re-download pretty much everything. > Not to mention that if there are multiple users on the same computer, > it'll happen again, each user ending up with his own copy of Moovida in > ~/.moovida/. > > I really hope that once you fix the tarball generation, you get back to > doing the same as for elisa : Release full tarballs even of the "light > releases" ;-)
+1. It's the same with Gentoo. Besides, I have the update_plugin_cache set to False; I understand that for Windows users and many people the automatic update thingy is preferable, but I really like to be the one that decides when my computer downloads or not stuff. Anyhow, great work! Moovida it's running relatively stable in my media center since it's release. Saludos. -- Canek Peláez Valdés Instituto de Matemáticas, UNAM
