All of lore.kernel.org
 help / color / mirror / Atom feed
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:40:46 +0100	[thread overview]
Message-ID: <4783A78E.9030405@gmx.net> (raw)
In-Reply-To: <1199798327.6053.11.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2096 bytes --]

Hi,
with Holger's help I pulled out an old version of libtool 1.5.6. I added
it to the tree again with DEFAULT_PREFERENCE = "-1" and a note for why
it exists ...

I'll have a look at unifying the libtool recipes later. They all look
very similar indeed ...

Regards
Robert

Richard Purdie schrieb:
> On Tue, 2008-01-08 at 13:29 +0100, Robert Schuster wrote:
>> on IRC it was suggested to put this on the mailing list.
>>
>> I want some osso versions (Maemo-specific) of some software packages in
>> OE to be able to build compatible packages:
>>
>> http://bugs.openembedded.org/show_bug.cgi?id=3384
>>
>> If no one objects I would like to apply the patches there.
> 
> I have two concerns:
> 
> a) libtool at least duplicates a lot of recipe, we should be encouraging
> more .inc usage.
> b) packages is becoming large and unwieldy
> 
> There could be a case for splitting packages into say:
> 
> packages/ 
> packages-gpe/
> packages-maemo/
> packages-openmoko/
> packages-opie/
> 
> Sadly these two points don't work well together since .inc/patch sharing
> with collections enabled doesn't work. This is something I think we need
> to fix as a priority.
> 
> The advantage to b) is I can then remove groups of files from the
> equation easily and speed up parsing and reduce the chances of bad
> things like  maemo packages breaking my normal ones...
> 
> This disadvantage is that you end up with libtool in two places and if
> one is updated, the other could be missed.
> 
> Reluctantly I'd therefore say it could be committed now if an .inc file
> is created for libtool and maybe improved for atk but we should consider
> the wider issue.
> 
> I'd also make a case for given vendor 'hacked' versions a
> DEFAULT_PREFERENCE = "-1" so you have to explicitly select them.
> 
> Cheers,
> 
> Richard
> 
> 
> 
> 
> 
> 
> _______________________________________________
> 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 --]

  reply	other threads:[~2008-01-08 16:47 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 [this message]
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

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=4783A78E.9030405@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.