Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>,
	"openembedded-devel@lists.openembedded.org"
	<openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-webserver][PATCH 1/1] webmin: drop allarch
Date: Wed, 25 Jun 2014 11:45:02 +0200	[thread overview]
Message-ID: <20140625094502.GT2437@jama> (raw)
In-Reply-To: <20140625092807.GA21830@ad.chargestorm.se>

[-- Attachment #1: Type: text/plain, Size: 2460 bytes --]

On Wed, Jun 25, 2014 at 11:28:07AM +0200, Anders Darander wrote:
> * Paul Eggleton <paul.eggleton@linux.intel.com> [140625 09:46]:
> 
> > On Tuesday 24 June 2014 09:54:12 Anders Darander wrote:
> > > * runtime dependencies are TUNE_PKGARCH causing do_package_write_*
> > >   task to have different signature for MACHINEs with different
> > >   TUNE_PKGARCH
> 
> > > -inherit allarch perlnative update-rc.d
> > > +inherit perlnative update-rc.d
> 
> > So apart from me being reticent to make this change at all (for reasons that 
> > we've discussed before), 
> 
> Yes, I'm well aware of those discussions. I was actually thinking about
> CC:ing you on my reply to Martin, after he suggested something like this
> change.
> 
> > there is another issue - allarch.bbclass does more than just setting
> > PACKAGE_ARCH, it also disables certain other functionality such as
> > debug symbol splitting which is superfluous for these kinds of
> > recipes; in my testing when I originally wrote the webmin recipe this
> > significantly reduced the time required to build the recipe. We can't
> > just drop this inherit without regard to that. (I'm sure the same
> > applies elsewhere, it's just that the size of webmin makes the impact
> > significant.)
> 
> I'm all for saving time! (And I'm not personally concerned by this
> issue, as I'm currently only using webmin in a build tree for a signle
> machine).

you can probably use allarch and assign
PACKAGE_ARCH = "${TUNE_PKGARCH}"
I don't remember how many savings will be disabled by this combination.

For multimachine builds these savings could be worse, because better to
spend a bit more time building everything just once per TUNE_PKGARCH and
don't touch it again (until the signature is changed) than keeping it
allarch, but still building it once per TUNE_PKGARCH (because of different
signature and then unpacking it from sstate *every-single-time* you're
building image for different MACHINE (so even without any change to
webmin recipe).

> Though, to get back to Martin Jansa's issue; if there isn't already an
> enhancment request file to the Yocto bugzilla, maybe it's time to file
> one regarding the possibillity of having an allarch package
> RDEPENDS/RRECOMMNEND a package with an ARCH or MACHINE tune...
 
There is one already:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5970

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

      reply	other threads:[~2014-06-25  9:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24  7:54 [meta-webserver][PATCH 0/1] webmin: Drop allarch Anders Darander
2014-06-24  7:54 ` [meta-webserver][PATCH 1/1] webmin: drop allarch Anders Darander
2014-06-25  7:45   ` Paul Eggleton
2014-06-25  9:28     ` Anders Darander
2014-06-25  9:45       ` Martin Jansa [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=20140625094502.GT2437@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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