Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modify mkpkg scripts to move packages to sources and add URL files #7

Open
demsullivan opened this issue Aug 1, 2014 · 3 comments
Open
Labels

Comments

@demsullivan
Copy link
Owner

OpenELEC's build system is designed around the idea that it automatically downloads OE-compatible source packages from a web server. This behaviour can be overridden by running the mkpkg script, moving the resulting package to OPENELEC_ROOT\sources and outputting a fake $PKG_NAME-$PKG_VER.tar.xz.url file to OPENELEC_ROOT\sources.

We'll need to edit each mkpkg script in tools/mkpkg and add the following to the end:

 echo "copying tar balls to sources..."
   if [ ! -d ../../sources/ ]; then
      mkdir ../../sources/
   fi
   if [ ! -d ../../sources/<name>/ ]; then
      mkdir ../../sources/<name>/
   fi
   mv <name>-$GIT_REV.tar.xz ../../sources/<name>/

 echo "generate md5 and url files..."
   cd ../..
   md5sum sources/<name>/<name>-$GIT_REV.tar.xz > sources/<name>/<name>-$GIT_REV.tar.xz.md5
   echo " http://sources.openelec.tv/devel/<name>-$GIT_REV.tar.xz" > sources/<name>/<name>-$GIT_REV.tar.xz.url
   echo "Source tar balls generated for <name> successfully."

Where <name> is the name of the package.

@demsullivan demsullivan added this to the initial-release milestone Aug 1, 2014
@demsullivan
Copy link
Owner Author

The other solution requires running a web server on the build machine and moving the packages to the webroot.

@demsullivan
Copy link
Owner Author

Ergh. The complication is that the mkpkg builds a package using the Git HEAD revision, but the OE build system uses the PKG_VERSION variable in the package.mk file to look for the source package.

Not sure how to circumvent this... maybe have the mkpkg file source the package.mk and use the PKG_VERSION to pull a specific Git revision?

@demsullivan
Copy link
Owner Author

Added this functionality in the build_addon script... the problem now is that Lakka comes with some patches that only apply to the specific rev it was built on. So either we toss out those patches, or we force the mkpkg script to grab the version specified in the package.mk file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant