From: Spider <spider@gentoo.org>
To: gentoo-dev <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] Gnome2 libtoolization
Date: Sat, 1 Jun 2002 15:18:35 +0200 [thread overview]
Message-ID: <20020601151835.549ec18a.spider@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 685 bytes --]
well,
as the moment of release prances forward I'm looking at the current
state of ebuilds.
right now we libtoolize a lot of gnome 2 except the core parts that is
glib atk gtk+ and pango, simply because they break with libtoolize...
fun isn't it?
Now, checking around a bit for libtoolize and asking some other gnome2
packagers, I got this reference:
http://www.redhat.com/mailing-lists/rpm-list/msg07002.html
odd.. isn't it?
I vote for dropping libtoolize along with debug info in or around the
20th
//Spider
t minus.... beep
--
begin .signature
This is a .signature virus! Please copy me into your .signature!
See Microsoft KB Article Q265230 for more information.
end
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2002-06-01 13:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-01 13:18 Spider [this message]
2002-06-02 20:41 ` [gentoo-dev] Gnome2 libtoolization Martin Schlemmer
2002-06-02 22:17 ` Spider
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=20020601151835.549ec18a.spider@gentoo.org \
--to=spider@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