On Mon, 29 Sep 2003 18:14:09 +0200 V> Johannes Winkelmann <jw@tks6.net> wrote:
Hi Simone,
Hi Johannes,
While I love crux' package management, I fear it might become hairy once binary packages are around; I'm certainly not afraid that you Simone will run into problems (as you know what it's all about), but if Joe User decides to check out crux and wants to install let's say evolution, pkgadd evolution#$VERSION.tar.gz will "just work", while the program won't. I assume there could be scripts to handle this, but it might be hard to forbid all users to use pkgadd directly. The joy of a system without dependencies in built packages ;-) So as a summary I think it's most important to communicate clearly that "binary packages for crux" doesn't mean "RPM-like packages for crux". I'm pretty sure we can reach this goal.
I can see your point and agree that the users shoul be clearly informed that pkgadd wouldn't suffice for CLC binaries. Incidentally, this is still valid for /opt packages, for example. I thought of a prt-get switch or something similar:
prt-get install `prt-get quickdep kdebase` --binary
PS: what about a "prt-get depinst portname" command that would automate the quickdep stuff? It used to be there and I removed it as I was afraid that it could imply
Hi, On Mon, Sep 29, 2003 at 18:57:25 +0200, Simone Rota wrote: this will not prevent Joe from doing prt-get install evolution --binary which will work fine... so prt-get should in this case print a warning "dependencies not satisfied". This is a dependency _checking_, something I don't want to do as long as we have informal dependencies. I was thinking of a new tool (another tool for a different kind of job) codenamed bininst which downloads and installs the package, using either a dependency matrix as http://sto.f2o.org/crux/wiki/DependencesMatrix when there's no ports tree around (think: installation), or prt-get's quickdep. Something like: bininst [-d deps.matrix] -u http://clc.berlios.de/packages evolution bininst would do the following: for each package from the dependency list: download from server (-u; could be configured in bininst.conf) pkgadd || exit on error Of course this could be integrated in prt-get, but for now I'd like to get a feeling of this first and I think a dedicated tool might help to distinuish as binary install vs. ports tree install are quite different. I hope I'll find some time this week to write a small prototype. that dependencies were working. You know, people usually don't bother reading the man page or even the manual, and it would be kind of frustrating to get "bug reports" about prt-get failing to install a package. The current way moved the responsibility away from me to the Packager ;-). Anyway, I guess I'll reintroduce it in one of the future versions. Regards, Johannes [...]
If you did not consider it up to now I'd strongly recommend using ccache. Inbetween minor releases of packages (the software) or new releases of the port, the speed gain is really huge.
Unfortunately I had some issue with ccache in the past: some port (icewm, ruby if I remember well) failed to compile; disabling ccache solved the prblem. Same here, OTOH those are only a handful of packages, and when I build new packages (as user first, rebuild with removed docs, root built) then ccache saves me a lot of time.
Regards, Johannes -- Johannes Winkelmann mailto:jw@tks6.net Biel, Switzerland http://jw.tks6.net