All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Andrea Adami <andrea.adami@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] cramfs: import recipe from meta-oe
Date: Tue, 11 Jun 2013 07:22:22 -0700	[thread overview]
Message-ID: <51B7329E.60101@linux.intel.com> (raw)
In-Reply-To: <CAAQYJAuWiym=7G_SY4QSO16+VBD4xRWAp5XroEKQd00dngaGCQ@mail.gmail.com>

On 06/11/2013 07:14 AM, Andrea Adami wrote:
> ping
>
> Maybe you want cramfs in recipes-devtools and not in recipes-support?
> Feedback, please
>
Apologies, we will not accept this recipe being moved into oe-core, 
there is not a strong case to move it to oe-core, cramfs is a image
type that is not heavily used, and the recipe is available in meta-oe.

Sau!

> Andrea
>
> On Tue, Jun 4, 2013 at 1:51 PM, Andrea Adami <andrea.adami@gmail.com> wrote:
>> Note there would be also the possibility to use the mkfs.cramfs
>> provided by util-linux implementing changes in image_types.bbclass and
>> util-linux itself.
>>
>> Seems a bit overkill to me but still an option...
>>
>> Andrea
>>
>> On Tue, Jun 4, 2013 at 1:39 PM, Andrea Adami <andrea.adami@gmail.com> wrote:
>>> ping
>>>
>>> Recipe is rather stable (tarball of v.1.1 dated 2002) and cramfs can
>>> be handy for read-only images on legacy devices.
>>>
>>> All the needed infrastructure is already present in
>>> image_types.bbclass so I'd say this recipe has been mistakenly
>>> forgotten when splitting out oe-core
>>>
>>>
>>> Andrea
>>>
>>> On Sun, May 26, 2013 at 1:23 AM, Andrea Adami <andrea.adami@gmail.com> wrote:
>>>> * though listed in IMAGE_FSTYPES the helper is missing so
>>>> * make oe-core autosufficient importing the recipe.
>>>> * Fix PN -> BPN to avoid fetch errors with cramfs-native
>>>>
>>>> Signed-off-by: Andrea Adami <andrea.adami@gmail.com>
>>>> ---
>>>>   meta/recipes-support/cramfs/cramfs_1.1.bb | 29 +++++++++++++++++++++++++++++
>>>>   1 file changed, 29 insertions(+)
>>>>   create mode 100644 meta/recipes-support/cramfs/cramfs_1.1.bb
>>>>
>>>> diff --git a/meta/recipes-support/cramfs/cramfs_1.1.bb b/meta/recipes-support/cramfs/cramfs_1.1.bb
>>>> new file mode 100644
>>>> index 0000000..0bca0e1
>>>> --- /dev/null
>>>> +++ b/meta/recipes-support/cramfs/cramfs_1.1.bb
>>>> @@ -0,0 +1,29 @@
>>>> +DESCRIPTION = "Builds cramfs filesystems for embedded systems"
>>>> +LICENSE = "GPLv2"
>>>> +LIC_FILES_CHKSUM = "file://COPYING;md5=393a5ca445f6965873eca0259a17f833"
>>>> +DEPENDS = "zlib"
>>>> +
>>>> +PE = "1"
>>>> +
>>>> +SRC_URI = "http://sourceforge.net/projects/cramfs/files/cramfs/1.1/${BPN}-${PV}.tar.gz"
>>>> +
>>>> +SRC_URI[md5sum] = "d3912b9f7bf745fbfea68f6a9b9de30f"
>>>> +SRC_URI[sha256sum] = "133caca2c4e7c64106555154ee0ff693f5cf5beb9421ce2eb86baee997d22368"
>>>> +
>>>> +EXTRA_OEMAKE = "\
>>>> +    'CC=${CC}' \
>>>> +    'CFLAGS=${CFLAGS}' \
>>>> +    'LDFLAGS=${LDFLAGS}' \
>>>> +"
>>>> +
>>>> +do_compile_prepend() {
>>>> +    ln -sf GNUmakefile Makefile
>>>> +}
>>>> +
>>>> +do_install() {
>>>> +    install -d ${D}${bindir}
>>>> +    install mkcramfs ${D}${bindir}
>>>> +    install cramfsck ${D}${bindir}
>>>> +}
>>>> +
>>>> +BBCLASSEXTEND = "native"
>>>> --
>>>> 1.8.1.5
>>>>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>


  reply	other threads:[~2013-06-11 14:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25 23:23 [PATCH] cramfs: import recipe from meta-oe Andrea Adami
2013-06-04 11:39 ` Andrea Adami
2013-06-04 11:51   ` Andrea Adami
2013-06-11 14:14     ` Andrea Adami
2013-06-11 14:22       ` Saul Wold [this message]
2013-06-11 15:41         ` Andrea Adami
2013-06-11 16:26           ` Bruce Ashfield
2013-06-11 21:25           ` Saul Wold

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=51B7329E.60101@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=andrea.adami@gmail.com \
    --cc=openembedded-core@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.