Migrate to nix-community

[adisbladis]

Hi!

Thanks for all this great work.

I'd like to move this repo over to https://github.com/nix-community/ to broaden the set of maintainers able to work on this package set.
I would also like create Hydra jobsets on https://hydra.nix-community.org/ so we can provide a binary cache for cross compiled remarkable packages using the nix-community builders.

Would you be open to moving this over to nix-community?

[adisbladis]

And a follow-up: I'd like to relicense this to MIT since that's what nixpkgs is using, and preferably at least some of the generic efforts should be moved there. Would you be fine with relicensing this work under MIT?

cc @siraben

[pl-semiotics]

Hi! Thanks for pinging me about this---I didn't/don't know much about nix-community. I will try to take a look into how that would work when I've next got a bit of time, hopefully this weekend or so, but I'm definitely open to it!

As to upstream, etc.---most of the work that's left in here is around packaging the "official" toolchain for the remarkable and hacking things to make it possible to run statically-linked nix-built executables on the device without having a whole nix store on the device. I have this set up mostly because I use it to build a number of things that I want to be able to run/distribute standalone, some of which hook into the implementation details of the stock software on the device enough that it's generally easier to use their compilers. As I understand it, the cross compilation infrastructure folks upstream aren't really interested in supporting that use case, so I don't know how much will be movable up there (Although there are a few fixes such as this one to make propagateBuildInputs play nicely with overrideAttrs that I've been meaning to submit upstream).

That said, I think I'm fine with relicensing under MIT. None of @siraben's code is actually in here, as much of it was subsumed by (and the rest was not rebased on) the big support RM2 commit, so I have the consent of all copyright holders. (I understand that they also used what I had here for the basis of a built-from-source-compilers-and-/nix-on-the-device approach and submitted it to upstream nixpkgs. I did not relicense the code to allow this (nor was I credited for it), and it has no bearing on the copyright or license status of the code in this repository.) I'll figure out how to officially update the license sometime soonish.

[adisbladis]

Hi! Thanks for pinging me about this---I didn't/don't know much about nix-community. I will try to take a look into how that would work when I've next got a bit of time, hopefully this weekend or so, but I'm definitely open to it!

I'm one of the admins of the nix-community org so I could organise this move together with you. I could also do any required work to do the hydra jobsets and all that.
I think the best way to do so is to ping me on either IRC (adisbladis @ freenode) if that's a possibility for you as I find real-time communication better for these kind of things.

That said, I think I'm fine with relicensing under MIT.

Great!

[siraben]

I understand that they also used what I had here for the basis of a built-from-source-compilers-and-/nix-on-the-device approach and submitted it to upstream nixpkgs.

@pl-semiotics The code used from the repo ended up mostly removed and only the addition of a system and the platform configuration was used (see https://github.com/NixOS/nixpkgs/pull/102503/files).

I did not relicense the code to allow this (nor was I credited for it).

Since I authored the PR, I apologize for the oversight. How would you like to be credited for it?

[teto]

would be cool to have this in nix-community. I like GPL, only the parts to integrate to nixpkgs would have to be relicensed to MIT ?
I might be able to help (write a flake/pin nixpkgs).