The first public Arch:e5 repository is available now! If you have no idea what E5 is, you may want to take a look at the post Announcing Arch:E5! first.
About one month passed and I just made the skel (or “skeleton”) repository available. It can be used to pacstrap a fairly minimal Arch:e5 installation. I’ll describe how to do that in a minute, but first a few words about what this actually is.
Arch uses a rather simple repository layout: The most important packages are in core and everything else is in extra. Packages not officially maintained by the project can probably be found in community. Disregarding a few special things this is already it.
While a “base” install of Arch is quite small compared to most well-known distros, it still pulls in quite a few things you might not want to have. Right, you can easily uninstall packages later. Or you could do without the “pacstrap” script and make use of pacman’s group feature. But using pacstrap is simply a very convenient way of installing Arch.
Now the idea is to allow for an installation that can be customized even more than Arch’s right from the beginning and thus split core into two repositories: skel and default. The former consists of everything absolutely necessary to get an Arch-based system up and running while the later holds the default packages that make the system actually useful.
The skeleton repository
Why would one do that split? Well, imagine you have a very specific idea of what your system should be. Perhaps you are an vi user. For what reason should nano even be installed at all? Or you don’t intend on using systemd. Why put it on your system in the first place?
Just pacstrapping the skeleton of your system together with what you actually want is a pretty obvious and comfortable solution.
E5 brings back one of the strong points of the classical Arch: rc.conf!
Right now skel contains all the packages which are in the “mini” group – 59 packages to be precise. I intend to put some more work into it to break it down to 50 packages at most (or rather: as few as possible). Some packages like the bootloader (syslinux) or the init-system (runit) are likely to be moved to the repository default in the future when E5 begins to offer alternative choices. Decreasing the number of packages could also be done by replacing some of them with others that have fewer dependencies.
How to install?
Warning: This ist just a preview. The system you’ll end up with is not of much use on its own at this time.
It doesn’t come with dhcp.
It doesn’t have a package manager.
It doesn’t even provide an editor.
If you want anything more than the bare skeleton, pacstrap it on top of E5 (from the Arch repositories) after the initial pacstrap is complete!
Preparing to pacstrap an Arch:e5 skeleton installation
As you can see, installing Arch:e5 is rather simple. Just boot from an Arch Linux live medium and make some changes to the /etc/pacman.conf file.
1. Comment out any Arch Linux repositories.
2. Then add the following:
SigLevel = Never
Server = http://www.elderlinux.org/repos/e5-skel
3. Once you saved the changes, you can check if pacman can read the package database using pacman -Sy. This is optional, of course, since the pacstrap script updates the db anyways.
4. Proceed with a more or less typical Arch installation:
Create and format your partitions, mount them and finally pacstrap the group mini instead of base. Then use genfstab and reboot. That’s it. If you follow the default partition layout, there’s no need to chroot to the environment since syslinux is installed automatically.
I’ll definitely continue working on E5. My next goal is currently to prepare and publish the default repository.
Content of skel
Since there’s not much in it, here’s the complete list of packages which skel currently holds (all but 3 packages were actually built with clang 3.4, btw.):
6 thoughts on “First public Arch:e5 repository published”
Interesante. lo felicito, la verdad segui los pasos que usted indica pero no me sirvio, me decia que hubo fallos en detectar el repo, es decir, ni con Pacman -Syu ni con pacstrap me funciono.
No se si es la distancia del guion en medio de e5-skel que en mi compu queda muy pegado, pero el error que arroja es que no detecta el repo.
Hi, Julio! Sorry for the delay of my reply, but I was busy on the weekend. Also I don’t really understand Spanish (learned some Italian years ago, but that’s unfortunately all I can offer when it comes to Romanic languages!) However it was not too hard to guess what you wrote.
All the E5 repositories were broken since my last update (for some reason the symlinks to the repo’s db files didn’t get uploaded). I’ve just fixed it. Now pacman (or pacstrap) should be able to access all of them (e5-skel, e5-default, e5-devel, e5-extra, e5-tex, e5-x11, e5-fltk and e5-gtk). And thanks for reporting the problem!
Ok, I used your repo again, but it failed, some packages can’t be downloaded.
So that I installed archlinux in the old form.
Hi Julio! Looks like there were a few more things messed up. Even if all the files would have been accessable, the db pointed to a broken kernel that could not boot properly… Now everything should finally be fixed (and I’ll avoid touching these repos again). I’ve installed a base and base-devel system from the repos and everything is working. The pacman package has been updated to include the x11, fltk and gtk repositories, too, and the ede package has been fixed. So for historical purposes, E5 will remain online for a while.
very interesting, i’m working with runit on arch too. Perhaps provide your pkgbuilds on github will be appreciate to known exactly what you are doing. just an idea.
Hi, Eric! This is all very old stuff by now – I did this more than 1.5 years ago and never updated the PKGBUILD files. Basically I eliminated systemd stuff from all packages and tried to use clang as the compiler (or dragonegg if clang wouldn’t work).
While I was pretty happy with how far I got with this (I had a fully graphical system with two desktop environments to choose from), not too many people were interested in the project. So I didn’t invest any more time to actually maintain things further and closed the project after accomplishing what I wanted to accomplish.
I can see if I can find the PKGBUILDs and upload them for you, though, if you really want them. I did something like E5 again, replacing glibc with musl, too. You can take a look at the PKGBUILDS (and other files) here: http://chiselapp.com/user/kraileth/repository/e5-musl/tree?ci=tip