All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] lib/oe/unpack.py: unpack rar archives
Date: Mon, 16 May 2011 16:00:36 +0200	[thread overview]
Message-ID: <4DD12E04.6050602@opendreambox.org> (raw)
In-Reply-To: <1305551007.5159.4.camel@mattotaupa>

On 05/16/2011 03:03 PM, Paul Menzel wrote:
> Am Montag, den 16.05.2011, 11:41 +0000 schrieb Andreas Oberritter:
>> Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
>> ---
>>  lib/oe/unpack.py |    2 ++
>>  1 files changed, 2 insertions(+), 0 deletions(-)
>>
>> diff --git a/lib/oe/unpack.py b/lib/oe/unpack.py
>> index 8e8bf36..fa517d8 100644
>> --- a/lib/oe/unpack.py
>> +++ b/lib/oe/unpack.py
>> @@ -96,6 +96,8 @@ def unpack_file(file, destdir, parameters, env=None):
>>              if dos:
>>                  cmd = '%s -a' % cmd
>>              cmd = "%s '%s'" % (cmd, file)
>> +        elif file.endswith('.rar'):
>> +            cmd = 'unrar x %s' % file
>>  
>>      if not unpack or not cmd:
>>          if os.path.isdir(file):
> 
> 1. What program needs this? I am just asking to be able to test this.

A recipe in a private layer.

> 2. Will `unrar-native` automatically be build when such an archive is
> encountered?

No. IIRC, adding that dependency created a non-trivial dependency
problem. I figured it would be preferrable to use the host's unrar.

> Acked-by: Paul Menzel <paulepanter@users.sourceforge.net>

Thanks,
Andreas



      reply	other threads:[~2011-05-16 14:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-16 11:41 [PATCH] lib/oe/unpack.py: unpack rar archives Andreas Oberritter
2011-05-16 13:03 ` Paul Menzel
2011-05-16 14:00   ` Andreas Oberritter [this message]

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=4DD12E04.6050602@opendreambox.org \
    --to=obi@opendreambox.org \
    --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.