All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schuster <theBohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev libtomcrypt: fix SRC_URI (close oebug 4159), bump to 1.17, fix staging
Date: Tue, 15 Apr 2008 13:02:36 +0200	[thread overview]
Message-ID: <48048B4C.5090805@gmx.net> (raw)
In-Reply-To: <20080415034950.982CC189218@amethyst.openembedded.net>

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

Hi.

xjqian commit schrieb:
> libtomcrypt: fix SRC_URI (close oebug 4159), bump to 1.17, fix staging

> * no idea why the previous maintainer leave do_install empty, but assuming there is a legit reason.
I recently stumbled upon libtomcrypt in another project may provide an
answer to this: libtomcrypt can be customized in many ways and chances
are good that if you just compile and install the library with default
settings those are wrong for the package that wants to use it.

The library's source is usually directly put into the package that uses
it (see asterisk, OpenTNL) and I am wondering whether it really makes
sense to have it in OE as a package.

Regards
Robert


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

       reply	other threads:[~2008-04-15 11:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080415034950.982CC189218@amethyst.openembedded.net>
2008-04-15 11:02 ` Robert Schuster [this message]
2008-04-15 23:28   ` [oe-commits] org.oe.dev libtomcrypt: fix SRC_URI (close oebug 4159), bump to 1.17, fix staging Junqian Gordon Xu
2008-04-15 23:35     ` Justin Patrin

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=48048B4C.5090805@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.