From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: add osso version of libtool and libatk
Date: Tue, 08 Jan 2008 17:41:59 +0100 [thread overview]
Message-ID: <4783A7D7.4020206@gmx.net> (raw)
In-Reply-To: <200801081527.09859.zecke@selfish.org>
[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]
Hi,
I can live with the plain versions, too. For libtool I re-added 1.5.6 as
discussed on IRC. I will prepare a similar patch for atk.
Holger Freyther schrieb:
> On Tuesday 08 January 2008 13:29:15 Robert Schuster wrote:
>> Hi,
>> on IRC it was suggested to put this on the mailing list.
>
> Hey,
> I don't like adding vendor hacked versions of standard software at all. I see
> the requirement you are facing but adding a Nokia hacked version is not the
> right way to do it.
>
> What are the differences you see? Can you extract the patch that is doing
> that? Is that patch a good idea and can be applied to our version of libtool?
>
>
> kind regards
> z.
>
>
> PS: I care more for libtool than atk+ (did they break API/ABI compability on
> it?)
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
prev parent reply other threads:[~2008-01-08 16:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-08 12:29 RFC: add osso version of libtool and libatk Robert Schuster
2008-01-08 13:18 ` Richard Purdie
2008-01-08 16:40 ` Robert Schuster
2008-01-08 14:27 ` Holger Freyther
2008-01-08 14:59 ` Stanislav Brabec
2008-01-08 17:08 ` Holger Freyther
2008-01-08 17:38 ` pHilipp Zabel
2008-01-08 18:03 ` Stanislav Brabec
2008-01-08 18:23 ` Holger Freyther
2008-01-08 16:41 ` Robert Schuster [this message]
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=4783A7D7.4020206@gmx.net \
--to=thebohemian@gmx.net \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.