Re: Stable GARNOME via arch
- From: Stef van der Made <svdmade planet nl>
- To: garnome-list gnome org
- Subject: Re: Stable GARNOME via arch
- Date: Sat, 12 Jun 2004 00:56:50 +0200
Dear Jeff,
I've found some updated packages for the unstable tree that I needed to
solve a bug with GCC-3.4.0 and some packages that where just a higher
version number which is just kewl :-) I'v been able to compile
successfully with these packages when running pachlevel 4 of the TLA branch.
Some updates for bootstrap
libtool is currently on version 1.5.6
freetype is version 2.1.8
fontconfig 2.2.95
and desktop to solve my issues with compiling on gcc-3.4.0
gnome-terminal-2.7.2
Cheers,
Stef
Nick Moffitt wrote:
begin Stef van der Made quotation:
Nick Moffitt wrote:
$ tla register-archive jdub perkypants org--projects http://www.gnome.org/~jdub/arch
$ tla get jdub perkypants org--projects/garnome--kenny--2.5.2
That was a usefull tutorial. 30 seconds and I was off compiling the
garnome release.
Happy to be of service.
Arch has a bit of a PR problem regarding its interface. A lot
of outdated docs are still up on the net from the days when it was
just a bunch of shell glue around Tom Lord's hackerlabs libraries.
Many steps that people moaned about in the arch and larch days are no
longer necessary in these days of tla.
As a matter of fact, you can actually shorten that first line
up there to just "tla register-archive http://www.gnome.org/~jdub/arch"
and tla will figure out the archive name automatically. In addition,
modern versions of tla will grab the most recent version of a package,
so you can just "tla get jdub perkypants org--projects/garnome--kenny"
without needing the --2.5.2 if you just want to get the latest
revision of the latest version.
Combine this with the fact that Tom's "Tutorial" is really
more of a reference for advanced developers, and you end up with
the perception that arch is really obscure and difficult. I highly
recommend that you look at the Wiki at http://wiki.gnuarch.org before
using the official documentation.
Also, people are writing wrappers around tla to provide more
features at a higher level than that at which tla operates. Check out
aba for more:
$ tla register-archive http://mirrors.sourcecontrol.net/jblack inframix com--2004/
$ tla get jblack inframix com--2004/tlacontrib--devo
$ mkdir -p ~/.arch-params/signing
$ echo '/usr/bin/tla-gpg-check gpg_command="gpg --keyserver pgp.dtype.org --keyserver-options auto-key-retrieve --verify-files -"' > ~/.arch-params/signing/\=default.check
btw tla signatures won't work because I can't compile gnupg stable
branch on slackware only the development realease seems to work.
Well, I'm using gnupg 1.2 for this. The big trick is to
figure out where gpg-check.awk is installed on your system. I used
/usr/bin/tla-gpg-check in the above example because that's where the
Debian tla package installs it. You may need to copy the awk script
to /usr/local/bin and adjust the =default.check file to match. It's
part of the official tla source distribution.
Anyway, this is an optional feature that wasn't even
*possible* with CVS (except in the sense that everything was
scriptable if you enforced a lot of horrible constraints on users and
servers everywhere).
I just moved the LNX-BBC (the original project for which I
wrote GAR) from CVS over to arch, and wrote up a tutorial for LNX-BBC
developers. It's up at:
http://lnx-bbc.org/arch.html
Check it out if you're curious as to what developers typically need to
do to setup. It's a few extra steps, but it never reaches 13. It's
also got a handy bibliography at the front listing the best bits of
the arch wiki.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]