Just another WordPress site

* Changed: adopted Ubuntu Feisty's packaging style and names and scripts for improved
compatibility in case of system upgrades (only for Feisty).

Envy uses a customised version of Ubuntu Feisty’s scripts to build the packages only if the OS is Feisty, otherwise the old scripts are used.

Hacking Ubuntu’s packaging scripts wasn’t so much fun but I really wanted to provide Envy with better compatibility with Ubuntu Feisty in case of system upgrades to Ubuntu Gutsy.
If you use Feisty you will notice the “new” packaging names:
nvidia-glx-new – the latest driver
nvidia-glx – the 96xx legacy driver
nvidia-glx-legacy – the 7xxx legacy driver

Unfortunately this new (and hopefully more compatible) packaging method comes at a price since it requires more dependencies (make sure you have a broadband Internet connection).

* Changed: Nvidia's -dev packages are now installed by default (only on Feisty).
The new packaging method makes it possible to install the nvidia-glx-dev package which some of you requested in the past.

* Changed: Envy is now aware of which packages are installed and decides what to do
accordingly

* Changed: Envy is now aware of which desktop manager is being used and tries to shut it
down (only in the textual installer) instead of trying to shutdown both gdm
and kdm blindly

* Changed: the error output is shown only when necessary otherwise it is hidden

These three changes refer to quite a few brand new code I have written for Envy. Thanks to the work I put into Envy in these days, Envy is now aware of which packages are installed and does no longer try to install or remove a package if such package is already installed (in the first case) or is not installed (in the second case).

Envy is also aware of what desktop manager you’re using (provided that it’s either gdm or kdm) and will stop it and restart it accordingly (only in the textual installer).

Athing which I disliked was the fact that Envy showed the output of the error (just warnings) of certain commands and led many users into thinking that something went wrong in the installation process (which was not the case). Now I can control the output of commands as I like.

12 thoughts on “Envy 0.9.7 is now available!”

module-assistant, interactive mode
Build of the package nvidia-new-kernel-source failed! How do you wish to proceed?
VIEW Examine the build log file
CONTINUE Skip and continue with the next operation
STOP Stop processing the build commands

Holy cow. I have no idea what the first paragraph of that first comment says but the accompanying message is exactly what I received as well. And now I am having serious trouble getting back to a working system. No matter how I edit xorg.conf, I either get black screen with an “out of range” warning or else the xserver simply fails and dumps me back to the command line.

I have already tried that. I even went back to the original xorg.conf. With all of the mucking around I’ve been doing in envy, my envy-installer.log is now almost 90k and 1300 lines long. I’m pretty sure you don’t want me posting that here. Can you email me? I’ll then attach it to a reply.