Running home-manager activation inside a nix build sandbox

[expipiplus1]

It would be great to be able to run the activation script from inside a nix-build sandbox.

This would be useful for running tests for one's dotfiles as I do here https://github.com/expipiplus1/dotfiles/tree/db638e7873fc10ad5e9a990f0612d0acbdd9d4c1/tests

I currently have something like this working, but it feels a little hacky in places: https://github.com/expipiplus1/dotfiles/blob/db638e7873fc10ad5e9a990f0612d0acbdd9d4c1/tests/home-test.nix#L69-L91

Hopefully it would be possible to make the activation script 'just work' inside such an environment (after setting HOME).

[stale]

Thank you for your contribution! I marked this issue as stale due to inactivity. If this remains inactive for another 7 days, I will close this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

• If this is resolved, please consider closing it so that the maintainers know not to focus on this.
• If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

• If you are also experiencing this issue, please add details of your situation to help with the debugging process.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

If you have nothing of substance to add, please refrain from commenting and allow the bot close the issue. Also, don't be afraid to manually close an issue, even if it holds valuable information.

Closed issues stay in the system for people to search, read, cross-reference, or even reopen--nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

[expipiplus1]

An alternative would be to just put the code I linked in a test to make sure that the existing ability to do it in a hacky way doesn't regress.

…

On Thu, 29 Apr 2021, 06:22 stale[bot], ***@***.***> wrote: Thank you for your contribution! I marked this issue as stale due to inactivity. If this remains inactive for another 7 days, I will close this issue. *Please read the relevant sections below before commenting.* *If you are the original author of the issue* - If this is resolved, please consider closing it so that the maintainers know not to focus on this. - If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. - If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue. *If you are not the original author of the issue* - If you are also experiencing this issue, please add details of your situation to help with the debugging process. - If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue. *Memorandum on closing issues* If you have nothing of substance to add, please refrain from commenting and allow the bot close the issue. Also, don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen--nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1717 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGRJXF2EAE35D3LRB2JJYDTLCDCDANCNFSM4V6U7NGA> .

[expipiplus1]

hmm, had a quick look but it seems a little tricky to fit this kind of meta test neatly into nmt. What are the options here?

[stale]

Thank you for your contribution! I marked this issue as stale due to inactivity. If this remains inactive for another 7 days, I will close this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

• If this is resolved, please consider closing it so that the maintainers know not to focus on this.
• If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

• If you are also experiencing this issue, please add details of your situation to help with the debugging process.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

If you have nothing of substance to add, please refrain from commenting and allow the bot close the issue. Also, don't be afraid to manually close an issue, even if it holds valuable information.

Closed issues stay in the system for people to search, read, cross-reference, or even reopen--nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

[expipiplus1]

still important.

[stale]

Thank you for your contribution! I marked this issue as stale due to inactivity. If this remains inactive for another 7 days, I will close this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

• If this is resolved, please consider closing it so that the maintainers know not to focus on this.
• If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

• If you are also experiencing this issue, please add details of your situation to help with the debugging process.
• If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

If you have nothing of substance to add, please refrain from commenting and allow the bot close the issue. Also, don't be afraid to manually close an issue, even if it holds valuable information.

Closed issues stay in the system for people to search, read, cross-reference, or even reopen--nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

[expipiplus1]

Still important

…

On Tue, 7 Dec 2021, 3:41 am stale[bot], ***@***.***> wrote: Thank you for your contribution! I marked this issue as stale due to inactivity. If this remains inactive for another 7 days, I will close this issue. *Please read the relevant sections below before commenting.* *If you are the original author of the issue* - If this is resolved, please consider closing it so that the maintainers know not to focus on this. - If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. - If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue. *If you are not the original author of the issue* - If you are also experiencing this issue, please add details of your situation to help with the debugging process. - If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue. *Memorandum on closing issues* If you have nothing of substance to add, please refrain from commenting and allow the bot close the issue. Also, don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen--nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1717 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAGRJXHSXBTHDOS4DYFG2CTUPUGVLANCNFSM4V6U7NGA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[rycee]

Agreed, I've been wanting this for the HM test suite as well. Sooner or later I'll get it fixed 🙂

[hab25]

I believe this would be very useful in lowering the amount of HM bugs, as well as bugs in users' own configuration.

[hab25]

Maybe this should, instead of being a nix build sandbox test, be a VM test implemented as a very light wrapper around https://nixos.org/manual/nixpkgs/stable/#tester-runNixOSTest . AFAICT this would be superior in all regards except performance.