From: Mikael Hallendal <hallski@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] The way to gnome2 by hand
Date: 20 Jan 2002 14:40:43 +0100 [thread overview]
Message-ID: <1011534043.1408.2.camel@fluffy> (raw)
In-Reply-To: <1011528015.24444.5.camel@wp.smile>
[-- Attachment #1: Type: text/plain, Size: 3058 bytes --]
sön 2002-01-20 klockan 13.00 skrev Sebastian Werner:
> Hey
>
> I try to build gnome 2 by hand before try to create ebuilds for this. I
> think i have the 50 % complete and want let you know the way. It's not
> so easy like gnome1 because the developers have split each libary in an
> own package. This is my current state in building gnome2 by hand:
Actually if you just want to test there is a module in gnome-cvs called
vicous-build-scripts which lets you build the entire gnome2 platfrom
from CVS with one command.
Due to some issue in our platform (Gentoo) you need to tweek your
modules.sh file some to make it run.
There are two things that I basically wait for before I do packages of
GNOME2.
1) GNOME 1.4.1 ( I could fix this without an actual release )
2) I need time and frankly, the alpha release pretty much sucks to use.
It might be OK for testing but I don't think anyone will be
impressed by it.
Regards,
Mikael Hallendal
> All configured with this script:
>
> -----------------------------
>
> G2PRE="/usr/gnome/2"
>
> PKG_CONFIG_PATH="$PKG_CONFIG_PATH:$G2PRE/lib/pkgconfig"
> export PKG_CONFIG_PATH
>
> ./configure --prefix="$G2PRE" --mandir=$G2PRE/share/man \
> --infodir=$G2PRE2/share/info --disable-debug --enable-threads $*
>
> ----------------------------------------------------
> sysconfdir is currently stored inside G2PRE/etc
>
> but i think it's ok to move it later to /etc/gnome2 or something
> ---------------------------------------------------------
>
> pkgname version flags
>
> glib 1.3.12
> atk 0.9
> pango 0.23
> gtk 1.3.12 --enable-shm --with-xinput=xfree
> linc 0.1.15
> libIDL 0.7.2
> ORBit2 2.3.102
> GConf 1.1.6
> bonobo-activation 0.9.3
> libbonobo 1.109.0
> gnome-mime-data 1.0.0
> gnome-vfs 1.9.4
> libgnome 1.109.1
> libart_lgpl 2.3.8
>
> libglade 1.99.5
> (cp libglade-1.99.5/libglade-convert /usr/gnome/2/bin/)
>
> libgnomecanvas 1.109.0
> libbonoboui 1.109.2
> libgnomeui 1.109.0
> gnome-common 1.2.4
> libwnck 0.2
> libzvt 1.109.0
>
>
> Greetings
>
> Sebastian
>
>
> --
> Sebastian Werner
> -
> http://www.werner-productions.de
> sebastian@werner-productions.de
> -
> Bismarckstraße 51
> 32427 Minden
> -
> Mobile: 0179.4590730
>
>
> --------------------------------------------------------------------------------
> Hey, waiter! I want a NEW SHIRT and a PONY TAIL with lemon sauce!
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
--
Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-01-20 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-20 12:00 [gentoo-dev] The way to gnome2 by hand Sebastian Werner
2002-01-20 13:40 ` Mikael Hallendal [this message]
2002-01-20 13:52 ` Sebastian Werner
2002-01-20 13:58 ` Mikael Hallendal
2002-01-20 14:05 ` Sebastian Werner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1011534043.1408.2.camel@fluffy \
--to=hallski@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox