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 Foundation on Value of GNU/Linux Skills

  • Jobs Report: Rapid Growth in Demand for Open-Source Tech Talent
    The need for open-source technology skills are on the rise and companies and organizations continue to increase their recruitment of open-source technology talent, while offering additional training and certification opportunities for existing staff in order to fill skills gaps, according to the 2018 Open Source Jobs Report, released today by The Linux Foundation and Dice. 87% of hiring managers report difficulty finding open-source talent, and nearly half (48%) report their organizations have begun to support open-source projects with code or other resources for the explicit reason of recruiting individuals with those software skills. After a hiatus, Linux skills are back on top as the most sought after skill with 80% of hiring managers looking for tech professionals with Linux expertise. 55% of employers are now also offering to pay for employee certifications, up from 47% in 2017 and only 34% in 2016.
  • Market value of open source skills on the up
    The demand for open source technology skills is soaring, however, 87% of hiring managers report difficulty finding open source talent, according to the 2018 Open Source Jobs Report which was released this week.
  • SD Times news digest: Linux Foundation releases open-source jobs report, Android Studio 3.2 beta and Rust 1.27
    The Linux Foundation in collaboration with Dice.com has revealed the 2018 Open Source Jobs Report. The report is designed to examine trends in open-source careers as well as find out which skills are the most in demand. Key findings included 83 percent of hiring managers believes hiring open source talent is a priority and Linux is the most in-demand open-source skill. In addition, 57 percent of hiring managers are looking for people with container skills and many organizations are starting to get more involved in open-source in order to attract developers.

GNU/Linux Servers as Buzzwords: "Cloud" and "IaaS"

  • Linux: The new frontier of enterprise in the cloud
    Well obviously, like you mentioned, we've been a Linux company for a long time. We've really seen Linux expand along the lines of a lot of the things that are happening in the enterprise. We're seeing more and more enterprise infrastructure become software centric or software defined. Red Hat's expanded their portfolio in storage, in automation with the Ansible platform. And then the really big trend lately with Linux has been Linux containers and technologies like [Google] Cooper Netties. So, we're seeing enterprises want to build new applications. We're seeing the infrastructure be more software defined. Linux ends up becoming the foundation for a lot of the things going on in enterprise IT these days.
  • Why next-generation IaaS is likely to be open source
    This is partly down to Kubernetes, which has done much to popularise container technology, helped by its association with Docker and others, which has ushered in a period of explosive innovation in the ‘container platform’ space. This is where Kubernetes stands out, and today it could hold the key to the future of IaaS.

Ubuntu: Snapcraft, Intel, AMD Patches, and Telemetry

  • SD Times Open-Source Project of the Week: Snapcraft
    Canonical, the company behind operating system and Linux distribution Ubuntu, is looking to help developers package, distribute and update apps for Linux and IoT with its open-source project Snapcraft. According to Evan Dandrea, engineering manager at Canonical, Snapcraft “is a platform for publishing applications to an audience of millions of Linux users.” The project was initially created in 2014, but recently underwent rebranding efforts.
  • Ubuntu 16.04 LTS Now Certified on Select Intel NUC Mini PCs and Boards for IoT Development, LibreOffice 6.0.5 Now Available, Git 2.8 Released and More
    Canonical yesterday announced that Ubuntu 16.04 LTS is certified on select Intel NUC Mini PCs and boards for IoT development. According to the Ubuntu blog post, this pairing "provides benefits to device manufacturers at every stage of their development journey and accelerates time to market." You can download the certified image from here. In other Canonical news, yesterday the company released a microcode firmware update for Ubuntu users with AMD processors to address the Spectre vulnerability, Softpedia reports. The updated amd64-microcode packages for AMD CPUs are available for Ubuntu 18.04 LTS (Bionic Beaver), Ubuntu 17.10 (Artful Aardvark), Ubuntu 16.04 LTS (Xenial Xerus), and Ubuntu 14.04 LTS (Trusty Tahr), "all AMD users are urged to update their systems."
  • Canonical issues Spectre v2 fix for all Ubuntu systems with AMD chips
    JUST WHEN YOU THOUGHT YOU'D HEARD THE END of Spectre, Canonical has released a microcode update for all Ubuntu users that have AMD processors in a bid to rid of the vulnerability. The Spectre microprocessor side-channel vulnerabilities were made public at the beginning of this year, affecting literally billions of devices that had been made in the past two decades.
  • A first look at desktop metrics
    We first announced our intention to ask users to provide basic, not-personally-identifiable system data back in February. Since then we have built the Ubuntu Report tool and integrated it in to the Ubuntu 18.04 LTS initial setup tool. You can see an example of the data being collected on the Ubuntu Report Github page.

Most secure Linux distros in 2018

Think of a Linux distribution as a bundle of software delivered together, based on the Linux kernel - a kernel being the core of a system that connects software to hardware and vice versa – with a GNU operating system and a desktop environment, giving the user a visual way to operate the system via a graphical user interface. Linux has a reputation as being more secure than Windows and Mac OS due to a combination of factors – not all of them about the software. Firstly, although desktop Linux users are on the up, Linux environments are far less common in the grand scheme of things than Windows devices on personal computers. The Linux community also tends to be more technical. There are technical reasons too, including fundamental differences in the way the distribution architecture tends to be structured. Nevertheless over the last decade security-focused distributions started to appear, which will appeal to the privacy-conscious user who wants to avoid the worldwide state-sanctioned internet spying that the west has pioneered and where it continues to innovate. Of course, none of these will guarantee your privacy, but they're a good start. Here we list some of them. It is worth noting that security best practices are often about process rather than the technology, avoiding careless mistakes like missing patches and updates, and using your common sense about which websites you visit, what you download, and what you plug into your computer. Read more