Foresight Linux – SE got a facelift, alot easier to find information for our swedish users. Thanks for all feedback.
Last newsletter was mostly to get information about developmet information. This newsletter is little more about system model and updated packages.
A new update mechanism called “system model” is added. In this model, a file called /etc/conary/system-model describes what should be installed on the system. This file is modified by certain conary update commands, and can also be edited with a text editor. The system model allows a system to be updated relative to a search path that includes groups as well as labels, leading to more coherent sets of updated packages. It also allows re-starting updates with transient failures; the filename /etc/conary/system-model.next is reserved for storing the system target state during an update operation.
The system model mode is intended to become the normal update mode for Conary-based systems in the future. It works by creating a set oftroves that define the system, and then moving the system to that defi‐nition. It is conceptually similar to building a group into a reposi‐tory and then migrating to that group. Significant differencesinclude:
- In a group, all trove references are absolute, but in a model,you can choose whether references are absolute. Migrating to aspecific version of a group will always move the system to theexact set of packages referenced, but re-applying a system modelwill update troves that are not pinned down to a specific ver‐sion.
- There is no group name for the set of troves.
- There is no version for the set of troves. (The version opera‐tion in a system model does not provide conary versioning.)
- Path and version conflicts are not checked when assembling theset of troves. (No group policy is run at all.) This meansthat path and version conflicts will be found only whileinstalling the packages.
A system model that installs only a single group will functionsimilar to migrate mode. The most obvious difference is that migratemode honors variations in byDefault settings in the system database(that is, an optional component of the trove(s) migrated to that hasbeen installed on the system will still be installed after the migrateoperation finishes), whereas a system model update honors those changesonly if they are represented in the model itself.
Next Foresight Linux iso will have system model enabled as default.
If you want to run it today in Foresight, open Terminal and write this command:
PackageKit is soon available as default in Foresight again. read more at: Og Maciel blog
To install it today, open terminal and write: sudo conary update PackageKit gnome-packagekit
GTK3 is now in Foresight Linux, first step against FL3 and Gnome 3.
Next release versions will be 2.5.1, 2.6 and 3.0
Picked out a few random packages that been updated during April month.
Audacious – 2.5.0
Banshee – 2.0.0
Chromium – 10.0.648.205
Emesene – 2.0 (built from git)
Firefox – 4.0
Flash-Player – 10.2.159.1
Hotot – 21-04-2011
Kupfer – v206
Nvidia - 270.41.06
Skype – 18.104.22.168
Transmission – 2.30b3
VLC – 1.1.9
Warsow – 0.61
Wine – 1.1.8
Latest review for Foresight Linux:
Last meeting: Concil meeting agenda 20-04-2011
Join the Foresight Community
Foresight users and developers are active on a number of different social networking sites.
- Follow a few Foresight developers every waking moment via Twitter or via identi.ca.
- Share pictures of your Foresight Linux desktop at the Foresight Linux Flickr group.
- Join the Foresight Linux group on Facebook.
- Add Planet Foresight Linux to your bookmarks or favorite feed reader, such as Liferea, to read blog updates from Foresight Developers.
- Join us at internet relay chat (irc). The Foresight Linux channels are hosted by the Freenode IRC network. #foresight
Contribute to the Foresight Linux Newsletter
Have a package or piece of software you want to share in the newsletter? Send it in! We are always looking for more writers or contributors.
We are also looking for volunteers to interview people in the Foresight and GNOME communities, links to news articles on the web or in print regarding Foresight Linux, and all the other content that makes up the newsletter.
Have thoughts or comments on the newsletter? Email tforsman at foresightlinux.org and your letter may be published in the next issue!