Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: cyril Romain <c.romain@laposte.net>
To: Using the OpenEmbedded metadata to build Linux Distributions
	<openembedded-devel@lists.openembedded.org>
Cc: Using the OpenEmbedded metadata to build Linux Distributions
	<openembedded-devel@openembedded.org>
Subject: Re: patcher changes - quilt patching breakage?
Date: Wed, 30 Aug 2006 20:08:46 +0200	[thread overview]
Message-ID: <44F5D42E.5060505@laposte.net> (raw)
In-Reply-To: <44F54AA0.9050901@dominion.kabel.utwente.nl>

Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jamie Lenehan schreef:
>   
>> On Tue, Aug 29, 2006 at 09:59:51AM +1000, Jamie Lenehan wrote:
>>     
>>> I've got huge amounts of breakage from quilt due to the patching
>>> related changs. Is anyone else seeing this. It looks like I can't
>>> apply any patches more than one.. which is rather wierd.
>>>       
>> The problem is that my build directory is:
>>
>>  /data/oe/build/titan-glibc-24
>>
>> and I have a directory called:
>>
>>  /data/oe/patches
>>
>> It appears that quilt searches throught he path for a directory
>> called "patches" and uses that for all it's patches. So the patches
>> are being stored in my /data/oe/patches directory instead of in the
>> package itself.
>>
>> The patch command used to mkdir the patches directory, but this is no
>> longer happening. The following patch appears to make things work
>> again - does this look correct to people who understand this patch
>> class?
>>     
>
> That patch isn't quite right yet, consider this recipe:
>
> - --------
> MAINTAINER = "Koen Kooi <koen@linuxtogo.org>"
> PV = ${DISTRO_VERSION}
>
> do_compile() {
>         mkdir -p ${D}${sysconfdir}
>         echo "Angstrom ${DISTRO_VERSION}" > ${D}${sysconfdir}/angstrom-version
>
> }
> - ---------
>
>
> that blows up. Does python have an os.mkdirhier?
>
>   
For that, python has os.makedirs(dir)

*makedirs*( 	path[, mode])

    Recursive directory creation function. Like mkdir(), but makes all
    intermediate-level directories needed to contain the leaf directory.
    Throws an error exception if the leaf directory already exists or
    cannot be created. The default mode is |0777| (octal). On some
    systems, mode is ignored. Where it is used, the current umask value
    is first masked out. *Note:* makedirs() will become confused if the
    path elements to create include os.pardir. New in version 1.5.2.
    Changed in version 2.3: This function now handles UNC paths correctly.

You you may also use bb.mkdirhier(dir)
____
def mkdirhier(dir):
    """Create a directory like 'mkdir -p', but does not complain if
    directory already exists like os.makedirs
    """

    debug(3, "mkdirhier(%s)" % dir)
    try:
        os.makedirs(dir)
        debug(2, "created " + dir)
    except OSError, e:
        if e.errno != 17: raise e
____


Regards,

  Cyril



  reply	other threads:[~2006-08-30 19:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-28 23:59 patcher changes - quilt patching breakage? Jamie Lenehan
2006-08-29  0:41 ` Jamie Lenehan
2006-08-30  8:21   ` Koen Kooi
2006-08-30 18:08     ` cyril Romain [this message]
2006-09-01  1:43     ` Jamie Lenehan

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=44F5D42E.5060505@laposte.net \
    --to=c.romain@laposte.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox