All of lore.kernel.org
 help / color / mirror / Atom feed
* can someone explain "git" versus "gitr" wrt PREFERRED_VERSION?
@ 2014-06-22 12:52 Robert P. J. Day
  2014-06-22 13:25 ` Martin Jansa
  2014-06-25 13:56 ` Paul Eggleton
  0 siblings, 2 replies; 3+ messages in thread
From: Robert P. J. Day @ 2014-06-22 12:52 UTC (permalink / raw)
  To: BitBake developer list


  possibly a stupid question but i've never let that stop me before.
still rummaging around in the bitbake user manual and looking through
the oe and poky codebase, and i notice examples like this (from poky).

  first, there's the recipe and PREFERRED_VERSION for drm:

meta/recipes-graphics/drm/libdrm_git.bb:
  SRCREV = "e01d68f9f3acfc35fe164283904b5d058c2ab378"
  PV = "2.4.40+git${SRCPV}"

meta-yocto/conf/distro/include/poky-floating-revisions.inc:
  #PREFERRED_VERSION_libdrm ?= "2.4.0+git${SRCREV}"

  also, the recipe and PFEFERRED_VERSION for libxcb:

meta/recipes-graphics/xorg-lib/libxcb_git.bb:
  SRCREV = "625ed596cae6dd8175aeb6cb6f26784928042f22"
  PV = "1.1.90.1+gitr${SRCPV}"

meta-yocto/conf/distro/include/poky-floating-revisions.inc:
  #PREFERRED_VERSION_libxcb ?= "1.1.90.1+gitr${SRCREV}"


  admittedly, the PREFERRED_VERSION settings for both of those are
commented out, but why does the first use:

  git${SRCREV}

while the second uses:

  gitr${SRCREV}

so what's with "git" versus "gitr"? i see no mention of this in the
bitbake user manual (would that be the right place to explain that?).
or is that covered in one of the higher-level yocto manuals?

  also (and i realize this is outside the scope of the bitbake
manual), i noticed the meta-oe layer adds another git-based version
selector in the gitpkgv.bbclass. is *that* documented anywhere? i
don't see a single mention of the phrase "gitpkgv" in any of the
current yocto docs.

  thoughts?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: can someone explain "git" versus "gitr" wrt PREFERRED_VERSION?
  2014-06-22 12:52 can someone explain "git" versus "gitr" wrt PREFERRED_VERSION? Robert P. J. Day
@ 2014-06-22 13:25 ` Martin Jansa
  2014-06-25 13:56 ` Paul Eggleton
  1 sibling, 0 replies; 3+ messages in thread
From: Martin Jansa @ 2014-06-22 13:25 UTC (permalink / raw)
  To: Robert P. J. Day; +Cc: BitBake developer list

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

On Sun, Jun 22, 2014 at 08:52:08AM -0400, Robert P. J. Day wrote:
> 
>   possibly a stupid question but i've never let that stop me before.
> still rummaging around in the bitbake user manual and looking through
> the oe and poky codebase, and i notice examples like this (from poky).
> 
>   first, there's the recipe and PREFERRED_VERSION for drm:
> 
> meta/recipes-graphics/drm/libdrm_git.bb:
>   SRCREV = "e01d68f9f3acfc35fe164283904b5d058c2ab378"
>   PV = "2.4.40+git${SRCPV}"
> 
> meta-yocto/conf/distro/include/poky-floating-revisions.inc:
>   #PREFERRED_VERSION_libdrm ?= "2.4.0+git${SRCREV}"
> 
>   also, the recipe and PFEFERRED_VERSION for libxcb:
> 
> meta/recipes-graphics/xorg-lib/libxcb_git.bb:
>   SRCREV = "625ed596cae6dd8175aeb6cb6f26784928042f22"
>   PV = "1.1.90.1+gitr${SRCPV}"
> 
> meta-yocto/conf/distro/include/poky-floating-revisions.inc:
>   #PREFERRED_VERSION_libxcb ?= "1.1.90.1+gitr${SRCREV}"
> 
> 
>   admittedly, the PREFERRED_VERSION settings for both of those are
> commented out, but why does the first use:
> 
>   git${SRCREV}
> 
> while the second uses:
> 
>   gitr${SRCREV}
> 
> so what's with "git" versus "gitr"? i see no mention of this in the
> bitbake user manual (would that be the right place to explain that?).
> or is that covered in one of the higher-level yocto manuals?

Read this thread:
http://lists.openembedded.org/pipermail/openembedded-core/2012-February/056558.html

>   also (and i realize this is outside the scope of the bitbake
> manual), i noticed the meta-oe layer adds another git-based version
> selector in the gitpkgv.bbclass. is *that* documented anywhere? i
> don't see a single mention of the phrase "gitpkgv" in any of the
> current yocto docs.

I think it's only documented in that .bbclass.

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

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: can someone explain "git" versus "gitr" wrt PREFERRED_VERSION?
  2014-06-22 12:52 can someone explain "git" versus "gitr" wrt PREFERRED_VERSION? Robert P. J. Day
  2014-06-22 13:25 ` Martin Jansa
@ 2014-06-25 13:56 ` Paul Eggleton
  1 sibling, 0 replies; 3+ messages in thread
From: Paul Eggleton @ 2014-06-25 13:56 UTC (permalink / raw)
  To: Robert P. J. Day; +Cc: bitbake-devel

Hi Robert,

On Sunday 22 June 2014 08:52:08 Robert P. J. Day wrote:
>   possibly a stupid question but i've never let that stop me before.
> still rummaging around in the bitbake user manual and looking through
> the oe and poky codebase, and i notice examples like this (from poky).
> 
>   first, there's the recipe and PREFERRED_VERSION for drm:
> 
> meta/recipes-graphics/drm/libdrm_git.bb:
>   SRCREV = "e01d68f9f3acfc35fe164283904b5d058c2ab378"
>   PV = "2.4.40+git${SRCPV}"
> 
> meta-yocto/conf/distro/include/poky-floating-revisions.inc:
>   #PREFERRED_VERSION_libdrm ?= "2.4.0+git${SRCREV}"
> 
>   also, the recipe and PFEFERRED_VERSION for libxcb:
> 
> meta/recipes-graphics/xorg-lib/libxcb_git.bb:
>   SRCREV = "625ed596cae6dd8175aeb6cb6f26784928042f22"
>   PV = "1.1.90.1+gitr${SRCPV}"
> 
> meta-yocto/conf/distro/include/poky-floating-revisions.inc:
>   #PREFERRED_VERSION_libxcb ?= "1.1.90.1+gitr${SRCREV}"
> 
> 
>   admittedly, the PREFERRED_VERSION settings for both of those are
> commented out

It's a good job that they are by the way, because a ${SRCREV} reference in 
PREFERRED_VERSION absolutely will not work. (We have % wildcard support in 
PREFERRED_VERSION to handle this situation.) 


> , but why does the first use:
> 
>   git${SRCREV}
> 
> while the second uses:
> 
>   gitr${SRCREV}
> 
> so what's with "git" versus "gitr"? i see no mention of this in the
> bitbake user manual (would that be the right place to explain that?).
> or is that covered in one of the higher-level yocto manuals?

gitr in PV is an old convention. I don't think it really warrants explanation, 
just use the current convention.

>   also (and i realize this is outside the scope of the bitbake
> manual), i noticed the meta-oe layer adds another git-based version
> selector in the gitpkgv.bbclass. is *that* documented anywhere? i
> don't see a single mention of the phrase "gitpkgv" in any of the
> current yocto docs.

Generally the Yocto Project manuals confine themselves to the things that the 
Yocto Project contributes to, and meta-oe isn't one of those things (at least, 
not directly or on a regular basis). So we wouldn't document gitpkgv.bbclass 
there. FWIW, people have asked for that class to be moved to OE-Core but 
Richard would prefer to implement it properly as an extension to the fetcher; 
we still have an enhancement bug open for that if anyone wants to dig into it:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=2872

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2014-06-25 13:56 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-06-22 12:52 can someone explain "git" versus "gitr" wrt PREFERRED_VERSION? Robert P. J. Day
2014-06-22 13:25 ` Martin Jansa
2014-06-25 13:56 ` Paul Eggleton

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.