Skip to content
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

Make this repository digga #431

Merged
merged 233 commits into from
Feb 26, 2022
Merged

Make this repository digga #431

merged 233 commits into from
Feb 26, 2022

Conversation

Pacman99
Copy link
Member

@Pacman99 Pacman99 commented Feb 23, 2022

closes: #430

This is just some git hacking to preserve both project's commit histories.

Commands that I ran:

git remote add digga git@github.com:divnix/digga
git checkout -b digga-main digga/main
git checkout -b merge-digga upstream/main
mkdir ../devos
mv * .editorconfig .envrc .gitignore ../devos/
mkdir examples
mv ../devos examples/
git add . && git commit -m "tree: move everything into examples/devos"
git checkout digga-main
git rebase merge-digga # there were 3 merge conflicts with src/pkgs-lib/shell, not sure why but that file has been deleted so I just delt with them
git checkout merge-digga
git merge digga-main --ff-only
git push upstream merge-digga

There are a lot of changes, so it'll be easier to review what exactly I did with git to get it this way.

The only actual changes I personally made:

  • removed .gitmodules and downstream submodule
  • move devos into examples/devos
  • removed bud template from devos and added devos template to digga

This doesn't cover devos docs, I think we will need a separate effort to merge devos docs into digga docs. Probably as a digga usage section or something. For now devos docs are just sitting in examples/devos.

This PR should theoretically have the same amount of commits being added as the number of commits in digga itself. I think it ended up being around 50 less because bors commits aren't included for some reason.

Pacman99 and others added 30 commits February 23, 2022 15:21
simple copy of devos library code
license is a copy from devos
they are still pretty unstable and can fatally break systems
includes filterPackages improvements
following same logic as exporting packages, but don't filter out inputs
Importers are auxiliary functions of this library. It feels inconsistent when
they have the same visibility of primary (builder) functions.
This means the functions output can be used as a module and imported in
mkFlake arguments
This sets shorthandOnlyDefinesConfig to false by default. Which means
those definitions can easily make use of the `imports` key. Without this,
they would have to pass a function to the options.
fixes devshell since lib no longer includes nixosSystem
allows `imports` key to be set without setting option as a function
This will always work and doesn't rely on fup features
```
$ btrfs subvol show / >/dev/null; printf "%s\n" "$?"
ERROR: Could not search B-tree: Operation not permitted
1
```

Btrfs's `ioctl()` `BTRFS_IOC_TREE_SEARCH` requires elevation.
`btrfs subvol show <path>` may be called by `nixos-generate-config`, and
if `btrfs subvol show <path>` fails then `nixos-generate-config` fails.

Fixes `flk up` failures due to the presence of Btrfs volumes.
includes api changes to fup
@Pacman99 Pacman99 self-assigned this Feb 23, 2022
@Pacman99
Copy link
Member Author

bors try

bors bot added a commit that referenced this pull request Feb 23, 2022
@bors
Copy link
Contributor

bors bot commented Feb 23, 2022

try

Build failed:

@Pacman99
Copy link
Member Author

bors try

bors bot added a commit that referenced this pull request Feb 23, 2022
@bors
Copy link
Contributor

bors bot commented Feb 23, 2022

try

Build failed:

@Pacman99
Copy link
Member Author

bors try

bors bot added a commit that referenced this pull request Feb 23, 2022
@bors
Copy link
Contributor

bors bot commented Feb 23, 2022

try

Build failed:

no need for submodules either
@Pacman99
Copy link
Member Author

bors try

bors bot added a commit that referenced this pull request Feb 24, 2022
@bors
Copy link
Contributor

bors bot commented Feb 24, 2022

try

Build succeeded:

@blaggacao
Copy link
Contributor

I can try tomorrow to do a git filter-repo merge of two unrelated histories whereby the devos history lands entirely in examples/devos, albeit all commits will be rewritten with the new subdir prefix.

Then, I can replay the manual changes that you did on top.

@Pacman99
Copy link
Member Author

I can try tomorrow to do a git filter-repo merge of two unrelated histories whereby the devos history lands entirely in examples/devos, albeit all commits will be rewritten with the new subdir prefix.

Then, I can replay the manual changes that you did on top.

I don't think that's a good idea because it would rewrite this repos git history which is never good for public branches. It would make sense if were merging devos into digga, but not when were doing it this way.

@blaggacao
Copy link
Contributor

blaggacao commented Feb 26, 2022

Ah! I see. I think I got lost first pass replaying your steps in my head. I then came under the impression commit history was lost, even if you explicitly stated otherwise. 🤷

Copy link
Contributor

@blaggacao blaggacao left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Grandioso!

@blaggacao
Copy link
Contributor

bors r+

In this case rather wake up with a unified Digga/DevOS.

Thank you!

bors bot added a commit that referenced this pull request Feb 26, 2022
431: Make this repository digga r=blaggacao a=Pacman99

closes: #430

This is just some git hacking to preserve both project's commit histories.

Commands that I ran:
```sh
git remote add digga git@github.com:divnix/digga
git checkout -b digga-main digga/main
git checkout -b merge-digga upstream/main
mkdir ../devos
mv * .editorconfig .envrc .gitignore ../devos/
mkdir examples
mv ../devos examples/
git add . && git commit -m "tree: move everything into examples/devos"
git checkout digga-main
git rebase merge-digga # there were 3 merge conflicts with src/pkgs-lib/shell, not sure why but that file has been deleted so I just delt with them
git checkout merge-digga
git merge digga-main --ff-only
git push upstream merge-digga
```
There are a lot of changes, so it'll be easier to review what exactly I did with git to get it this way.

The only actual changes I personally made:
 - removed .gitmodules and downstream submodule
 - move devos into examples/devos
 - removed bud template from devos and added `devos` template to digga

This doesn't cover devos docs, I think we will need a separate effort to merge devos docs into digga docs. Probably as a digga usage section or something. For now devos docs are just sitting in `examples/devos`.

This PR should theoretically have the same amount of commits being added as the number of commits in digga itself. I think it ended up being around 50 less because bors commits aren't included for some reason.

Co-authored-by: Parthiv Seetharaman <pachum99@myrdd.info>
Co-authored-by: Pacman99 <pachum99@gmail.com>
Co-authored-by: David Arnold <dar@xoe.solutions>
Co-authored-by: Pacman99 <pachum99@myrdd.info>
Co-authored-by: Dusk Banks <me@bb010g.com>
Co-authored-by: Pacman99 <Pacman99@users.noreply.github.com>
@bors
Copy link
Contributor

bors bot commented Feb 26, 2022

Timed out.

@Pacman99
Copy link
Member Author

bors r+

@bors
Copy link
Contributor

bors bot commented Feb 26, 2022

Build succeeded:

@bors bors bot merged commit 8a77ad7 into main Feb 26, 2022
@bors bors bot deleted the merge-digga branch February 26, 2022 07:23
@Pacman99 Pacman99 mentioned this pull request Mar 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

This repository is now digga!