Re: [oe-commits] org.oe.dev libtomcrypt: fix SRC_URI (close oebug 4159), bump to 1.17, fix staging

Re: [oe-commits] org.oe.dev libtomcrypt: fix SRC_URI (close oebug 4159), bump to 1.17, fix staging

[Robert Schuster]

[-- 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 --]

Re: [oe-commits] org.oe.dev libtomcrypt: fix SRC_URI (close oebug 4159), bump to 1.17, fix staging

[Junqian Gordon Xu]

On 04/15/2008 06:02 AM, Robert Schuster wrote:
> 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.

Thanks. so the recipe is just a template for people who wants to use it. 
   I will just leave it there until somebody with strong opinion 
suggests otherwise.

Regards
Gordon

Re: [oe-commits] org.oe.dev libtomcrypt: fix SRC_URI (close oebug 4159), bump to 1.17, fix staging

[Justin Patrin]

On Tue, Apr 15, 2008 at 4:28 PM, Junqian Gordon Xu <xjqian@gmail.com> wrote:
>
> On 04/15/2008 06:02 AM, Robert Schuster wrote:
>  > 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.
>
>  Thanks. so the recipe is just a template for people who wants to use it.
>    I will just leave it there until somebody with strong opinion
>  suggests otherwise.
>

I'm pretty sure that PHP links to it for its mcrypt extension.

-- 
Justin Patrin