Ease restrictions on installing into non-empty site directories.
Review Request #12997 — Created April 30, 2023 and updated
rb-site install
will now permit installing into a site directory that
contains only avenv
folder. This is to enable deployments where a
virtual environment is first set up in the destination sitedir, and then
the installedrb-site
is used to populate the sitedir.There's also a
--allow-non-empty-sitedir
option for advanced use,
which bypasses the empty sitedir check.
Tested installing into a populated sitedir. It gave me the expected error.
Tested installing into a new location. Installation was allowed.
Tested installing into a directory containing just a
venv
directory.
Installation was allowed.Tested installing into an empty directory. Installation was allowed.
Tested installing into a populated sitedir and using
--allow-non-empty-sitedir
. Installation was allowed.
Summary | ID |
---|---|
250004ff338b8ff4146c06cba12e4ce04dfa4726 |
Description | From | Last Updated |
---|---|---|
I think it's somewhat confusing to have the conditional be in the assignment to site_contents. How about we do: site_contents … |
david |
- Testing Done:
-
+ Tested installing into a populated sitedir. It gave me the expected error.
+ + Tested installing into a new location. Installation was allowed.
+ + Tested installing into a directory containing just a
venv
directory.+ Installation was allowed. + + Tested installing into an empty directory. Installation was allowed.
+ + Tested installing into a populated sitedir and using
+ --allow-non-empty-sitedir
. Installation was allowed.
- Change Summary:
-
Simplified the logic for determining whether a directory can be installed into.
- Commits:
-
Summary ID 3fc1ba7366fdcc779a7180267883d9c1341f8d83 250004ff338b8ff4146c06cba12e4ce04dfa4726 - Diff:
-
Revision 2 (+42 -6)