Language Selection

English French German Italian Portuguese Spanish

Your rPath to Conary

Filed under
Linux
Reviews
-s

Development Release: rPath Linux 0.51 (Alpha) was announced by DistroWatch yesterday, and I was a bit curious. After my first glance, I was a bit taken aback. rPath doesn't seem to be targetting desktop users. Although it ships with KDE and Gnome, they aren't the most up-to-date versions, nor are they dressed up or enhanced in any manner distinguishable. In my humble opinion, I think rPath is probably a developer's platform, ...a conary developer's platform.

Information about rPath, as well as its ancestor Specifix, is fairly sketchy. The rPath website is a page listing a job opening and a link to the conary wiki, however DistroWatch states "rPath is a distribution based around the new Conary package management, created by ex-Red Hat engineers, to both showcase the abilities Conary provides and to provide a starting point for customisation." The conary wiki is pretty thin itself, although I was able to gleen a little information from it.

It was no big surprise to see (a modified) Anacoda as the installer and (as usual) I found it fairly straight forward and easy to complete. It asks some basic configuration questions such as network setup, firewall choice, and bootloader conf. I must say I loved the package selection portion. One is give one choice: everything. Could it be any easier? It takes a little while to install and once it's complete, it reboots without setting up other hardware or user accounts. Upon reboot it starts X as root, but to complete some other basic configurations in a graphical environment using rPaths Setup Agent. Included configurations include the date and timezone, monitor and resolution, and of course user account(s). Upon Finish, it restarts X and presents gdm for login. KDE and gnome are about your only choices for a desktop environment/window manager. rPath includes KDE-3.4.1 and Gnome-2.10.2. The Xserver version is xorg-6.8.2, gcc is 3.3.3, and the kernel is 2.6.12.5. The kernel-source isn't installed from the iso, but one can install it with conary.

        

Conary is rPath's package management system. As it appears conary is the focus of rPath, I spent quite a bit of time trying to figure it out. I began my quest quite lost and confused and ended it a little less lost and confused. According to the site, "Conary is a distributed software management system for Linux distributions. It replaces traditional package management solutions (such as RPM and dpkg) with one designed to enable loose collaboration across the Internet." Simply put, it's the package manager. It appears to be able to obtain packages from different repositories, utilizing binaries if available or sources if necessary and storing all versionings in a database in order to track changes from source branch all the way back to local versions installed on a given system to meet dependencies without conflicts.

According to the wiki, after the installation of rPath 0.51 the first thing one should do is update conary to version 0.62.2. Termed Conversion, the instructions stated to issue the following commands:

$su -
# conary update conary
# conary q conary
$ su
# sed -i 's/lockTroves/pinTroves/g' /etc/conaryrc

They continue with instructions in case an AssertionError is encountered. I didn't experience such an error and proceded with reading the wiki, --help, and man pages.

Conary at the commandline appears very apt-like. In fact the conary-gui is identical in appearance to synaptic. The gui front-end didn't seem to function very well here, but the commandline version seems to work as intended. Also included is the utility "yuck" which is a wrapper script to call conary --upgradeall.

        

Fortunately running conary is much easier than trying to understand what it is or how it works. Some simple commands include: conary q <packagename> reveals if the given packagename is installed, whereas conary rq <packagename> lists the newest available upgrade. conary update <packagename> installs or updates requested packagename, and conary erase <packagename> uninstalls. There are many many interesting options to play with in using conary beyond those basics, but most seem to geared toward package builders. Some of these include emerge, which builds the "recipe"; commit, which stores the changes; and showcs, which shows the difference. It really looks sophisticated and yes, I admit, a little complicated at the more in-depth level.

So, to install the kernel-source, one simply types: conary update kernel-source

The developers might be onto a superior package management system, but is it catching on? We know rPath obviously uses it and I understand Foresight Linux to utilize this package management system. As for rPath, it was a stable functional development environment. It seems it isn't trying to be the latest or greatest nor the prettiest. If you are interested in developing for conary or wish to use a system utilizing that package management system, then rPath might be the distro for you. The full package list as tested is HERE.

        

Conary

I'm pretty hazy on this too, so I might be completely off, but here is how I understand this:

While to a casual user Conary looks pretty much like apt-get or synaptic, it does do something more advanced under the hood. It is intended to make it easy to put together a system using a number of separate and *independent* repositories, each making its own changes and mini-releases. Conary tracks not only what you installed on your system, but also where it came from. This extends to any dependencies it uses, and it becomes quite a powerful concept.
For example, Foresight which also uses Conary is actually created largely from packages pulled directly from rPath repos; I would say as much as 75% of packages are not modified at all. If you install Foresight and later run updates on it, you'll see number of packages are updated from rPath repos. Any packages Foresight guys developed themselves come from their own repositories, naturally. But any packages that do exist in rPath but were modified in Foresight are overlayed over the 'standard' versions, with Conary keeping track of what comes from where, and what depends on what (in that context). This is pretty cool for Foresight guys, who can make their own distro while at the same time take a lot from the base, rPath.

Think of it this way: if you used Fedora, you probably tried at some stage to add various third-party repos to your yum config: Livna, Freshrpms etc... and quite possibly you discovered in the process some of them can conflict with others... it can become a mess. Well, this is exactly the situation Conary adresses.

... but again, I could be completely wrong.

re: Conary

That's pretty much the way I understand it as well, in that conary can keep track of any and all changes to the branches of a given source from the main branch all the way to minor revisions on public mirrors as well as on your local machine (which is especially good for developers). An end user can choose to install any version listed or just go with the latest. Like other package managers, all depends on the repositories set up tho. Good explanation! Thanks for your contribution. That's wonderful.

-s

----
You talk the talk, but do you waddle the waddle?

Conary

You are correct that rPath is developmnent release for the extensive testing of the Conary system, fPath is from Specifix who is the creator of Conary. Other distros like Foresight have taken and used it for their own needs. I find the Conary system interesting and quite functional, but have not made a decision about it's need and potential in the comunity.

My 2cents,
Capnkirby

re: Conary

I think it's a wonderful concept as well, but I think it'd be rather complicated to set up and most developers are already set in their ways. And when you factor in how few distros use that method... I don't think it's something that will catch on right away.

----
You talk the talk, but do you waddle the waddle?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Linux Plumbers Conference and Kernel Developments in METRICFS, FS-Cache, HWMON

  • Application Ecosystem Microconference Accepted into 2020 Linux Plumbers Conference

    We are pleased to announce that the Application Ecosystem Microconference has been accepted into the 2020 Linux Plumbers Conference! The Linux kernel is the foundation of the Linux systems, but it is not much use without applications that run on top of it. The application experience relies on the kernel for performance, stability and responsiveness. Plumbers is the perfect venue to have the kernel and app ecosystems under one roof to discuss and learn together and make a better application experience on the Linux platform.

  • Google Opens Patches For "METRICFS" That They Have Used Since 2012 For Telemetry Data

    The METRICFS file-system has been in use internally at Google since 2012 for exporting system statistics to their telemetry systems with around 200 statistics being exported per machine. They are now posting the METRICFS patches as open-source for review and possible upstreaming. A "request for comments" on METRICFS was sent out today on the Linux kernel mailing list. Their motives for now finally publishing these patches is as a result of the recent Statsfs proposal by a Red Hat engineer for a RAM-based file-system for exposing kernel statistics to user-space. METRICFS has a similar aim to Statsfs.

  • FS-Cache Rewritten But Even Its Developers Are Hesitant About Landing It For Linux 5.9

    FS-Cache provides the Linux kernel with a general purpose cache for network file-systems like NFS and AFS but also other special use-cases like ISO9660 file-systems. FS-Cache has been rewritten for better performance and reliability, among other benefits, and while it has been sent in as a pull request for Linux 5.9 even its own developers provide some caution over landing it this cycle. FS-Cache has seen work to "massively overhaul" it with a variety of improvements. The new and improved FS-Cache will now use async direct I/O in place of snooping for updated pages that in turn means less virtual memory overhead. The new FS-Cache implementation has simpler object management, changes to object invalidation, and a variety of other work.

  • Corsair Commander Pro Driver Sent In To Linux 5.9

    The hardware monitoring (HWMON) subsystem has a new driver that is likely to excite some enthusiasts wanting greater control over thermal monitoring and fan control for their systems. The previously covered Corsair Commander Pro Linux driver is now coming with Linux 5.9. The Commander Pro offers six 4-pin fan ports with PWM controls, two RGB LED channels, and four thermal sensors. An interested user/developer created this Linux driver without the support from Corsair. The thermal and fan control support is in place with this new HWMON driver while the RGB lighting controls are available from OpenRGB.

Graphics: Mesa 20.1.5, Intel and AMD

  • mesa 20.1.5
    Hi all,
    
    I'd like to announce Mesa 20.1.5, the fifth bugfix release for the 20.1 branch.
    
    The next bugfix release is planned for 2 weeks from now, on 2020-08-19.
    
    Cheers,
    Eric
    
    
  • Mesa 20.1.5 Released For The Latest Stable Open-Source Vulkan / OpenGL Drivers

    Mesa 20.1.5 provides the latest stable open-source Vulkan/OpenGL graphics drivers for the Linux desktop as the newest bi-weekly milestone. Mesa 20.2 remains under development as this quarter's feature release due out in about one month's time. Mesa 20.2 is running behind schedule as it should have been branched around the end of July but has yet to happen. In any case, more Mesa 20.2 feature work continues to land and more than likely will ship sometime in September. But until that occurs, Mesa 20.1 is the latest stable series.

  • Intel Workaround For Graphics Driver Regression: "The Platform Problem Going Crazy"

    Sent out over the weekend was a patch series for the Intel Linux kernel graphics driver entitled "Time, where did it go?" This set of 42 patches aims to provide incremental improvements to the driver to offset a performance regression in Linux 5.7 that Intel hasn't been able to track down. This increased complication of the driver to offset the regression is now under the microscope. The set of 42 patches by longtime Intel open-source developer Chris Wilson provides incremental improvements to reduce the execution latency. He was upfront that the intent of these improvements are to "basically offsets the small regressions incurred when compared to [Linux kernel] 5.7."

  • RadeonSI Resorts To Disabling SDMA For GFX9/Vega Due To APU Issues

    AMD's RadeonSI Gallium3D driver has resorted to disabling SDMA (System DMA) async DMA engine support for all GFX9/Vega hardware due to issues plaguing some APUs. While SDMA has the potential of helping performance, GFX9 (Vega) is now seeing the support disabled due to bugs seeming to only affect APUs. Though it's not entirely surprising as the open-source AMD Radeon Linux driver also is not enabling SDMA at this point for GFX8 (Polaris) or GFX10 (Navi) hardware either. Opened three months ago was the merge request for disabling SDMA on GFX9 and to back-port it to the stable series as well. Longtime AMD open-source developer Marek Olsak noted, "This is somewhat a radical step. All opinions welcome."

Audiocasts/Shows: Destination Linux, FLOSS Weekly, CrowPi and Linux Headlines

           
  • Destination Linux 185: Let’s Fix Linux Tech Support

    On this week’s episode of Destination Linux, we’re transitioning from the topic of Bug Reporting last week to Tech Support in Linux this week. We’re going to check in on Wayland’s progress with Plasma’s new release, we have an sandbox MMO for gaming, and our popular tips/tricks and software picks. All of this and so much more, coming up right now on Destination Linux.

  •                 
  • FLOSS Weekly 590: Rensselaer Center for Open Software - A Community of Open Source Developers

    RCOS is a group of RPI students who work on open-source projects. The goal of RCOS is to empower students to develop open-source solutions to real-world problems. They have created 300+ open source projects over the years. Doc Searls and Simon Phipps talk with Wes Turner, a Senior Lecturer in the Department of Computer Science at Rensselaer Polytechnic Institute (RPI) and the Director of the Rensselaer Center for Open Source. They discuss teaching open source and the hardships that come along with that, especially with e-learning. They also discuss what the future could look like if we could have more open-source programs like RCOS in other universities.

  •        
  • The Best Raspberry Pi Laptop Kit | CrowPi 2 Review

    The Best Raspberry Pi Laptop Kit | CrowPi 2 Review of the kit, usage, and examples. 

  •        
  • 2020-08-05 | Linux Headlines

    LibreOffice 7 dodges its rebranding controversy, the Pinta bitmap editor sees its first new version in 5 years, Red Hat accommodates certification seekers with new pandemic-friendly rules, and ownCloud 10.5 brings background sync changes to the platform.

Gaming on Linux in 2020: Way Better Than You Think

Linux has always been seen as a rather rigid operating system for gaming. Many games used to be unavailable on Linux, and the ones that you could play used to have all sorts of bugs. However, the situation’s not the same anymore with Ubuntu 20.04. The OS is way better for gaming than you may think. In certain situations, games even run better on Linux than on Windows. This is quite impressive so let’s see what lead to Linux’s improvements. Read more Also: Narrative-driven adventure Impostor Factory has new teaser trailer