WIP: feat: support for x86_64-linux #1
No reviewers
Labels
No labels
Compat
Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: auxolotl/labs#1
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/x86-64_linux"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently I'm formatting with
nixfmt-rfc-style
since no formatter is specified, let me know if you would like me to reformat with another formatter.feat: inital support for x86_64-linuxto feat: support for x86_64-linuxpotluck
isn't ready to be used by anything just yet, I'm currently working out issues with the module system (there seems to be some trouble around submodules). Can we revert the changes inpotluck/
for now?@ -23,1 +17,3 @@
};
forEachSystem = lib.attrs.generate [
"i686-linux"
"x86_64-linux"
Pretty much all of the packages from
stage1
and beyond are restricted toi686-linux
. I don't think that adding the extra system here will do much unless we modify packages to build properly onx86_64-linux
and set theirmeta.platforms
to include the new system.e0eeb90446
toe068db6843
e068db6843
toc2143518d7
This is the correct thing to do, thanks!
Probably we should make another PR to add that as the specified formatter
Perhaps we can add a nix-shell script. I would like to avoid adding any dependencies to these projects.
This is fine, though it's made the PR a little hard to follow since it is also introducing platform changes. I think the only changes right now are to meta.platforms?
Yea I'm wondering if we want to pull out the format and move it into a separate PR (maybe not worth the trouble here). We should also add something about formatting before each commit to our standards. Maybe we could write a pre-commit hook or similar? This should be easy if we're standardizing treefmt (me, @minion and @dfh (on the forums) are writing a module for it).
So long as we don't introduce additional inputs to the projects then I am down! I'd like to keep these all self-contained.
This seems likely to be an extremely annoying restriction, unless we use something like niv instead... would you be OK with a separate "dev" flake (i.e. allowing us to have development inputs as well as regular ones)?
c2143518d7
tofe8157bd15
feat: support for x86_64-linuxto WIP: feat: support for x86_64-linuxCurrently getting an error with gnutar-boot
61139839b6
to7adf088998
7adf088998
to786738b368
786738b368
to7adf088998
7adf088998
toe1ca419046
e1ca419046
to3332f332b9
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.