On Thu, Sep 01, 2016 at 02:28:04PM +0200, shraptor wrote:
> ...
>
> >we of course intend to document all steps needed to setup the CI,
> >something we can expect to be accomplished in the first quarter of
> >2017, so that people can also build their own.
>
> So is this the only way to setup a too
...
we of course intend to document all steps needed to setup the CI,
something we can expect to be accomplished in the first quarter of
2017, so that people can also build their own.
So is this the only way to setup a tool chain for armhf on devuan?
I got to research some more.
I only want
hay Scooby
On Thu, 01 Sep 2016, shraptor wrote:
> That is old greek to me unfortunately.
you seem to translate it pretty well :^) anyway yes, apologies for the
brevity, I was writing while on the road.
> pinthread I guess is this one https://github.com/nexlab/pinthread
> and the
On 2016-08-31 09:21, Jaromil wrote:
for package building we are still using the "legacy" arm-sdk scripts,
the SDK is still work in progress that should merge all the efforts
going in the same direction by parazyd, katolaz and me
to re-build packages you need to setup jenkins with the
devuan-jenk
dear shraptor,
On Tue, 30 Aug 2016, shraptor wrote:
> I want to build packages for a rpi3
>
> I wonder if there is something to re-use from
>
> https://git.devuan.org/devuan/arm-sdk
>
> It is used in auto-build of devuan iso for rpi.
arm-sdk has nothing to do with package build,
it deals wi
I want to build packages for a rpi3
I wonder if there is something to re-use from
https://git.devuan.org/devuan/arm-sdk
It is used in auto-build of devuan iso for rpi.
In the instruction for arm-sdk If I follow the recipe down to
; init devuan raspi2
Am I close to having an environment fo
