I'm a maintainer of upstream Libva and Libva-intel-driver. I have moved our projects from freedesktop.org to github.com. Wiki location has moved to: https://01.org/linuxmedia/vaapi Libva project has moved to https://github.com/01org/libva Use https://github.com/01org/libva/issues/new to file bugs on the libva github site Intel driver project has moved to https://github.com/01org/intel-vaapi-driver Use https://github.com/01org/intel-vaapi-driver/issues/new to file bugs on the intel-vaapi-driver github site Recipes will need to be updated to pull source from the new github repos mentioned above. Thanks, Sean
A couple of questions: Will the freedesktop.org tarballs remain for some know period of time? We have older releases that still rely on freedesktop.org Moving foward with 01org, will there be a tarball generated at each release? If not, can you please inform us when releases occur so that we can update the SRCREV to a tagged release SHA
(In reply to comment #1) > A couple of questions: > > Will the freedesktop.org tarballs remain for some know period of time? We > have older releases that still rely on freedesktop.org > > Moving foward with 01org, will there be a tarball generated at each release? > If not, can you please inform us when releases occur so that we can update > the SRCREV to a tagged release SHA Hi, Yes, the tarballs will remain at freedesktop.org, indefinitely. Yes, if you are familiar with github, tar balls can easily be pulled from releases. Thanks, Sean
Very familiar with github, but git changes the timestamp and thus the checksum of git based tarballs, so I will just convert these to git based recipes and provide GIT SHAs for SRCREV when it's updated.
Merged the libva change to oe-core: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=73d1c2713725602549fff99434be24fe593d80bb and into meta-intel here for libva-intel-driver: http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/commit/?id=0c2da994195b4db36db80258d09d0e5faed22136 Both now use the github repo directly and when updates occur we will need to update the SRCREV SHAs