From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ee0-f49.google.com (mail-ee0-f49.google.com [74.125.83.49]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id E2390E00801 for ; Fri, 20 Dec 2013 01:34:01 -0800 (PST) Received: by mail-ee0-f49.google.com with SMTP id c41so921941eek.8 for ; Fri, 20 Dec 2013 01:34:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=q3EzfiRyoDAC+gMtIgFsmBDZibvPRwWcYsFFLQch11s=; b=watEnwygJYBla2/jyJtNXwPfT3gxyGHx80KSG/NvdWyBwuRPmxpSOVAfb0mu/HLW/s wi66tJoyAtgGrdeLzm1tyTfDfOiJWon7wKAiMGJjnLq1Of/B4q1IVJGva7aFqzQBgwTi O8uTM4F6iYZKvz13uwKuCkTWQJa+I3umMcmvq7KSFHQpI/Qky6XAA55+URBFzMSXz6ou F6EvLibB2/x+LaoC/jIC+xiCdTv8ks9GYu3+QEUqMiiRo4jzv1faVsFworzXTHQ+Wlrj uibZvS/2c8WyZ6Lc4ispoHsYiVAkSHmyMnH7x1D9DcQku+NbaOKHUz5mUecFxA9eDsEg ZSZw== X-Received: by 10.14.251.132 with SMTP id b4mr1693792ees.78.1387532040615; Fri, 20 Dec 2013 01:34:00 -0800 (PST) Received: from localhost (ip-89-176-104-107.net.upcbroadband.cz. [89.176.104.107]) by mx.google.com with ESMTPSA id o47sm16860282eem.21.2013.12.20.01.33.59 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Dec 2013 01:33:59 -0800 (PST) Date: Fri, 20 Dec 2013 10:34:33 +0100 From: Martin Jansa To: Brad Litterell Message-ID: <20131220093433.GQ3706@jama> References: <14453943.1Qpn4azGq8@helios> <20131218093624.GK3706@jama> MIME-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.5.22 (2013-10-16) Cc: Paul Eggleton , "yocto@yoctoproject.org" Subject: Re: Setting PV dynamically in a recipe X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto Project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Dec 2013 09:34:05 -0000 X-Groupsio-MsgNum: 17602 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7Rldj+JZnTQmDdGi" Content-Disposition: inline --7Rldj+JZnTQmDdGi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 20, 2013 at 03:09:31AM +0000, Brad Litterell wrote: > Hi Martin, >=20 > I decided just to create my own feature list: >=20 > MY_FEATURES=3D"debug" >=20 > and I can happily query it in my custom recipes. >=20 > However, I haven't quite figured out the best way to taint the status has= hes for my packages so that changes to this flag force a rebuild. I origin= ally tried putting the marking in PR, which works for causing the right thi= ngs to rebuild, but when I switch from debug to release, I get errors like = this: >=20 > ERROR: Package version for package my-config-files went backwards which w= ould break package feeds from (0:2.0.0.0-r0-debug to 0:2.0.0.0-r0) >=20 > Is there a way I can taint my recipes so that changing MY_FEATURES causes= them all to be evaluated as out of date. I don't care if that causes some= extra rebuilds when I switch MY_FEATURES - I care more about avoiding the = error message. Or is there a way I can turn off this particular error mess= age on specific recipes? Depends on where you're using MY_FEATURES variable in the recipe, in most cases it should be included in sstate signature and rebuilt automatically (with the same version) when MY_FEATURES is changes. If you're using latest oe-core, that error is QA check, which can be disabled with SKIP_INSANE (per package) or moved from ERROR_QA to WARN_QA in distro config. > ________________________________________ > From: Martin Jansa [martin.jansa@gmail.com] > Sent: Wednesday, December 18, 2013 1:36 AM > To: Brad Litterell > Cc: Paul Eggleton; yocto@yoctoproject.org > Subject: Re: [yocto] Setting PV dynamically in a recipe >=20 > On Wed, Dec 18, 2013 at 01:29:25AM +0000, Brad Litterell wrote: > > Hi Paul, > > > > Thanks for that tip. For my private packages I don't build directly fr= om git, but from a tarball (in turn created from my working directory) beca= use I want to be able to build the source I'm working on without committing= it to git. > > > > In an ideal world, I'd like to to be able to build in two modes: dev & = release. Release mode would use the git-based solution (and enforce buildi= ng from git), and in the dev mode, build from something like externalsrc. = (The reason I don't use externalsrc directly is because it didn't detect ch= anges in the underlying external source, so I created a script that does an= d updates the tarball.) > > > > What is the best way to switch recipes between dev & test modes like th= at. It appears debug-tweaks is only used in image recipes, so I don't know= whether I should (or could) use something like this in a package recipe: > > > > SRC_URI +=3D '${@base_contains("EXTRA_IMAGE_FEATURES", "debug-tweaks", = "...tarball...", "...git..."}' > > > > or whether something like that is asking for trouble. My current solut= ion is manual - edit the recipe, but that feels kinda lame. > > > > It seems like most of the yocto build tools assume building directly fr= om git (or with external-src but without dependency checking). > > > > Any suggestions? >=20 > Don't use *IMAGE_FEATURES* to in recipe conditionals. >=20 > When you're building some package you don't know in which image it will > be included so you cannot know with which *IMAGE_FEATURES* it should be > built. >=20 > It's true that EXTRA_IMAGE_FEATURES are often set in DISTRO config, but > still it's unsafe to assume they are "global". With improved > base_contains and sstate interaction, using some flag in DISTRO_FEATURES > shouldn't cause so many packages to rebuild, so it could be usable for > "debug-build" flag. >=20 > > ________________________________________ > > From: Paul Eggleton [paul.eggleton@linux.intel.com] > > Sent: Tuesday, December 17, 2013 12:24 PM > > To: Brad Litterell > > Cc: zhenhua.luo@freescale.com; yocto@yoctoproject.org > > Subject: Re: [yocto] Setting PV dynamically in a recipe > > > > Hi Brad, > > > > On Tuesday 17 December 2013 19:46:11 Brad Litterell wrote: > > > Thank you for the reply. However, That's not what I'm looking for. I > > > already get the latest version of the source code. > > > > > > What I'm really after is the ability to generate output packages that= have > > > increasing version numbers so I can use the package manager to update= them. > > > > > > I think Martin's subsequent reply is the secret to use PKGV. I didn'= t know > > > about that variable. > > > > You don't need to use any special classes to get this behaviour. Put th= is in > > your recipe (replacing 1.2.3 with the appropriate base version you are > > building): > > > > PV =3D "1.2.3+git${SRCPV}" > > > > and enable the PR service, which will ensure SRCREV changes always incr= ement > > the version properly: > > > > http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#wor= king-with-a-pr-service > > > > Cheers, > > Paul > > > > -- > > > > Paul Eggleton > > Intel Open Source Technology Centre > > _______________________________________________ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto >=20 > -- > Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com --=20 Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com --7Rldj+JZnTQmDdGi Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlK0DykACgkQN1Ujt2V2gByKbwCeKIHNBbYuterfDOQCvoFj1EoR HUUAoLrkVcIsQDCdLXMOyidYSJOeOtMV =Huk3 -----END PGP SIGNATURE----- --7Rldj+JZnTQmDdGi--