From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: <package>-static name conflict with some recipes
Date: Fri, 28 May 2010 08:28:16 +0200 [thread overview]
Message-ID: <htnnq0$75p$1@dough.gmane.org> (raw)
In-Reply-To: <20100528052720.GA15949@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 28-05-10 07:27, Khem Raj wrote:
> Hi
>
> I have seen that we have parallel recipes for some applications for static
> build
> called package-static.bb like below
>
> ./dialog/dialog-static_1.1-20080819.bb
> ./busybox/busybox-static_1.2.1.bb
> ./busybox/busybox-static_1.11.3.bb
> ./kexec-tools/kexec-tools-klibc-static_1.101.bb
> ./kexec-tools/kexec-tools-klibc-static_2.0.1.bb
> ./zaurus-utils/nandlogical-klibc-static_1.0.0.bb
> ./klibc/klibc-utils-static_1.5.15+1.5.16.bb
> ./klibc/klibc-utils-static_1.5.18.bb
> ./klibc/klibc-utils-static_1.5.15.bb
> ./klibc/klibc-utils-static_1.5.bb
> ./klibc/klibc-utils-static_1.5.17.bb
> ./skype/skype-static_2.0.0.72.bb
> ./udev/udev-static-devices.bb
> ./udev/udev-static_124.bb
>
> Now they conflict with the automatic package that we generate to bundle
> static libraries. Since the the packages which bundle static libraries
> are essentially development packages may be they should be called
>
> <package>-dev-static instead of <package>-static
>
> IMO that will avoid the conflict and also clarify the package content
> a bit
>
> Thoughts?
Fine by me, as long as the usermanual gets updated as well.
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFL/2KAMkyGM64RGpERAggiAJ42dgqQTw1Lvkn9falV7gHh6Oxa4QCgovkL
+wtAjJHnqEXObVlm7nAW77Y=
=dbFD
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2010-05-28 6:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 5:27 <package>-static name conflict with some recipes Khem Raj
2010-05-28 6:27 ` Frans Meulenbroeks
2010-05-28 6:28 ` Koen Kooi [this message]
2010-05-28 7:44 ` Andrea Adami
2010-08-19 21:41 ` Andrea Adami
2010-10-26 7:49 ` Andrea Adami
2010-10-26 9:11 ` Frans Meulenbroeks
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='htnnq0$75p$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.