On Wed, 11 May 2016, Ozi Traveller wrote:
> I did a an install and setup up last night in a vm, and I need to install
> a couple of packages that weren't in the instructions: git-core, zsh.
ACK. will add those
> I managed to get sdk-init to work, after some fiddling.
>
> I did sdk-chroot-arch amd64 which looked successful, but sdk-chroot-build
> failed with errors.
I know this part is currently under re-factoring because many things
have changed in the past 2 years. This SDK was useful to completely
bootstrap Devuan at a time in which our repositories did not
exist. Now the situation is far better and I plan to drop some code
and functionalities to have a more lean and modular system.
in particular the package building part should be refactored to work
with git-buildpackage, to optionally import debian packages from
alioth and then finally to offer a local repository of built packages
for the chroot.
I'm planning to do this in the coming months, but cannot provide an
exact schedule.
> It would be good, if there was someone who has this working to do a step
> by step to do the setup. Also to do a build too, because the instructions
> aren't clear.
you are welcome to propose corrections wherever you think they should
be. With exception for the package building part which has to be
rewritten.
> If devuan-sdk is the way forward for creating an iso, then I'd like to
> understand it better.
it is one of the ways forward and is provided for people wanting to
prepare custom isos with custom packages. Please note we have
modularised the whole setup so now there is:
- devuan-sdk : local chroot and package build (TODO refactor)
- vm-sdk : takes any iso (also devuan-sdk) and build various VM images
- arm-sdk : takes any iso (also devuan-sdk) and build various ARM images
> In terms of features, will the sdk replace live-build at some stage?
I think that will be another module, live-sdk, and will likely be
built on top of refracta scripts. Parazyd is investigating this now
and proposing to fsmithred some changes to enhance interoperability
with our setup, lets see how that goes. I'd like to have fsmithred
included in our team to maintain it, but maybe he doesn't want to get
involved that much.
ciao