Closed Cyanoxygen closed 11 months ago
@Cyanoxygen Plus, when using custom tarballs, Ciel will not perform this check (likely, not tested).
With existing Ciel workspaces (which does not have arch
configured, Ciel will crash.
@Cyanoxygen Plus, when using custom tarballs, Ciel will not perform this check (likely, not tested).
I can load any OS I want by ciel load-os
with the custom tarball, after manually running ciel init
and ciel config -g
.
If running ciel new
with a custom tarball, Ciel will still ask for target architecture - this is pending to be fixed, the desired behavior is to fallback to host architecture.
ciel new
apparently fails to use tarballs located outside its workspace. It appears to skip the download yet still attempts to extract the empty archive prepared for downloading.
![]()
ciel new
apparently fails to use tarballs located outside its workspace. It appears to skip the download yet still attempts to extract the empty archive prepared for downloading.
I think this hsould be moved to a new issue.
ciel new
apparently fails to use tarballs located outside its workspace. It appears to skip the download yet still attempts to extract the empty archive prepared for downloading.
@chenx97 Please build against the latest commit and test it, this issue should be fixed with this commit.
Review applied, please review the changes again.
With this PR users can now specify the target architecture when creating a Ciel workspace using
ciel new
, and when loading OS tarball usingciel load-os
.ciel new
, Ciel will ask the user for the desired target architecture.ciel new
, Ciel will skip this question.ciel load-os
, Ciel will not ask for the target architecture.Fixes #17.