-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LineageOS 18.1 #96
LineageOS 18.1 #96
Conversation
Thanks! Looks fairly straightforward. There's one thing I was hoping we could do (in a future PR if you'd rather not deal with it now): |
Thanks for your great work hmenke! I'm running 18.1 built with this code. 18.1 is still a bit buggy and missing some functionality like Xposed, which is only available for Android 10 right now. I agree that 17.1 should remain an install option. |
50e8fd7
to
1f82b90
Compare
@danielfullmer Done. In the previous LineageOS update you mentioned
Do you have a script for that, so that I can do that too for 18.1? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The updater scripts would need some changes to support both lineage-17.1
and lineage-18.1
. A couple obvious things I can see: update-device-metadata.py
should produce device-metadata.json
with devices supporting either branch, instead of filtering for just one branch. The update-device-dirs.py
script should take the branch as an argument, and device-dirs.json
and vendor-dirs.json
should be split into files supporting the 17.1 and 18.1 branches, with the nix expression choosing which one to use.
@hmenke Here's what I had used in the past: let
pkgs = import ./pkgs {};
lib = pkgs.lib;
deviceMetadata = lib.importJSON ./flavors/lineageos/device-metadata.json;
in
map (device: (import ./default.nix {
inherit pkgs;
configuration = {
inherit device;
flavor="lineageos";
};
}).config.build.checkAndroid )
(lib.attrNames (lib.filterAttrs (n: v: v.branch == "lineage-17.1") deviceMetadata)) Preferably we'd remove the filterAttrs part so we'd check all devices using their supported branch. |
How is this PR going so far?, is anyone still working on it? |
I've just pushed up a new The notable one is this: f859b08 I'm currently building @Kranzes Thanks for the reminder. I had intended to look more closely at this, but got distracted with other things. |
Update: |
All 166 devices were able to build |
ffe463a
to
907eebd
Compare
I've fixed the evaluation error, followed your recommendation of unifying |
Co-authored-by: Daniel Fullmer <danielrf12@gmail.com> Co-authored-by: Adrian Parvin D. Ouano <adrianparvino@gmail.com>
This is just a change of default. By default, it will now fetch the manifest file each time, with --resume being the option to go back to the old behavior. Nix output hashes can still be cached and recovered from the oldrepojson options.
We use the information about the default branch for each device from LineageOS/hudson. The updaters also now try to fetch both branches for each devices, to allow the user to try an unsupported (newer or older) branch for their device.
@hmenke Rebased and pushed changes to your branch. Unless there are any issues I've missed. I think this should be good to merge. If anyone has another device to that they'd like to test LineageOS 18.1 with, it would be nice to confirm that it works for others. |
https://lineageos.org/Changelog-25/