Closed star-buck closed 9 years ago
koko never finishes initializing
still not building: https://launchpad.net/~blue-shell-next/+archive/ubuntu/builds/+packages
can't build because it is downloading files from the internet which is disallowed and cannot be overridden.
so... right now cmake checks in cmake_current_binary_dir if the files are there. this path is potentially different across different builds (it definitely is across different architectures). what we need is cmake to also check in $cmake_source_dir/data or some other source bound path where we can provide the data so that cmake doesn't need to download them. this ultimately will then also be the path where the data would be put for a release tarball.
@vishesh: can you fix this?
On Thu, Feb 12, 2015 at 3:16 PM, apachelogger notifications@github.com wrote:
can't build because it is downloading files from the internet which is disallowed and cannot be overridden.
Are you sure it cannot be?
I understand the need for this for the final release, but for CI systems?
so... right now cmake checks in cmake_current_binary_dir if the files are there. this path is potentially different across different builds (it definitely is across different architectures). what we need is cmake to also check in $cmake_source_dir/data or some other source bound path where we can provide the data so that cmake doesn't need to download them.
done
It checks in the source directory.
this ultimately will then also be the path where the data would be put for a release tarball.
Yup. But we aren't creating release tarballs right now.
Vishesh Handa
so can it be packaged correctly now?
build seems still failing: https://launchpad.net/~blue-shell-next/+archive/ubuntu/builds/+sourcepub/4775584/+listing-archive-extra
should be fixed now
@apachelogger : please ship in next KCI (preferably vivid from now on).
packaged and finally starts, but shows no files (will do a new ticket for that saga to continue...)
ship in KCI or make package in blueshellnext