Thursday 11. January, 2007
(I was going to write this as a response to a comment on an earlier post but I thought this would make a nice posting)
Conary is a package manager software, like dpkg+apt-get in Debian/Ubuntu (and so on..) or RPM+yum/SmartPM…. The difference to tradiotional ones is that Conary has integrated repository and it doesn’t have external wrappers around repositories like apt-get or yum. Conary is written in Python (entirely?).
Answer to question “What issues did you have with Conary”:
I already had over 600 RPM specs for one thing (of which about 200 are generated by a script, does X.Org ring a bell?) (This, of course, is not Conary’s fault)
The way Conary repositories are handled… I got that impression that there’s no way to remove packages from the repository, which makes it “quite big”, if I have to rebuild packages 1) when updating and 2) when I notice (too late) that something is wrong in current package or 3) if have included a package that has legal troubles, how do I get rid of it without rebuilding the whole repository?
I guess that all *possible, future* mirrors would have to be running Conary service, which would limit the number of server candidates to near zero.
Setting it up isn’t the easiest task, especially when made from Ubuntu.
Creating new package recipes does seem to be easy, but then I got fed up with all these build policies. My initscript package ended up having not a single working script as all symbolic links were screwed, when the policy changed things to the “RedHat-way”. And it also required chkconfig(?) lines into the scripts, but LFS doesn’t contain such a thing. And it seems that Conary wiki has no information on how to change policies with exception of just making exception definitions into recipes, which doesn’t seem right and sustainable. (I can modify RPM to have some kind of package cleaning policy in post-spec-build macros and it’s not hard)
Of course there’s other (and even better) ways to build a Conary-based distribution as suggested in the Wiki (Installing a Conary-based distribution and modifying it from there…), but that would drop out the LFS and even BLFS to limited extent.
Don’t misunderstand me, Conary does have nice properties such as simple recipes, but sometimes there’s little things that make it undesirable.
Wednesday 10. January, 2007
Once again a year has passed by, and what did I do. Nothing, nothing to show. In March 2006 I started working on “Prospekt Linux”, a never finalized project of creating a Linux distribution version basing on Linux From Scratch -books.
At the same time I created a bunch of Bash scripts (later to become J Package Manager) that later got translated into Python (with exception of buildpkg-script, which is still a Bash-script).
Originally Prospekt Linux was meant to use JPM as it’s package manager, but due to frustration a switch was made to RPM Package Manager (I did try Conary, but it sucked). Maybe we can see the release of Prospekt Linux 0.1 this year?
The School started also. It’s so different in the University, it’s the second week and still no lectures (This may have something to do with my choices…).
I also started using XFire while in Windows (It was because of pure curiosity (and the obsessive need to register into all kinds of services))