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

Remove mentions of “home project” in documentation and comments #3547

Merged
merged 3 commits into from
Aug 13, 2023
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 2 additions & 3 deletions src/Pkg.jl
Original file line number Diff line number Diff line change
Expand Up @@ -539,9 +539,8 @@ The logic for what path is activated is as follows:
activate the environment at the tracked path.
* Otherwise, `s` is interpreted as a non-existing path, which is then activated.

If no argument is given to `activate`, then activate the home project.
The home project is specified by either the `--project` command line option to
the julia executable, or the `JULIA_PROJECT` environment variable.
If no argument is given to `activate`, then use `LOAD_PATH` to determine the
project to activate.
Socob marked this conversation as resolved.
Show resolved Hide resolved

# Examples
```
Expand Down
2 changes: 1 addition & 1 deletion src/REPLMode/command_declarations.jl
Original file line number Diff line number Diff line change
Expand Up @@ -304,7 +304,7 @@ PSA[:name => "activate",
activate [--shared] path
activate --temp

Activate the environment at the given `path`, or the home project environment if no `path` is specified.
Activate the environment at the given `path`, or use `LOAD_PATH` to determine the project to activate if no `path` is specified.
Socob marked this conversation as resolved.
Show resolved Hide resolved
The active environment is the environment that is modified by executing package commands.
When the option `--shared` is given, `path` will be assumed to be a directory name and searched for in the
`environments` folders of the depots in the depot stack. In case no such environment exists in any of the depots,
Expand Down
2 changes: 1 addition & 1 deletion test/api.jl
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ using ..Utils
cd(mkdir("tests"))
Pkg.activate("Foo") # activate developed Foo from another directory
@test Base.active_project() == joinpath(path, "modules", "Foo", "Project.toml")
Pkg.activate() # activate home project
Pkg.activate() # activate LOAD_PATH project
@test Base.ACTIVE_PROJECT[] === nothing
end end
end
Expand Down
2 changes: 1 addition & 1 deletion test/new.jl
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ Pkg._auto_gc_enabled[] = false
source053 = pkg.source
source053_time = mtime(pkg.source)
end
# - The home project was automatically created.
# - The active project was automatically created.
@test haskey(Pkg.project().dependencies, "Example")
@test length(Pkg.project().dependencies) == 1
# Now we install the same package at a different version:
Expand Down
2 changes: 1 addition & 1 deletion test/repl.jl
Original file line number Diff line number Diff line change
Expand Up @@ -260,7 +260,7 @@ temp_pkg_dir() do project_path
pkg"activate --shared Foo" # activate existing shared Foo
@test Base.active_project() == joinpath(tmpdir, "Project.toml")
pop!(Base.DEPOT_PATH)
pkg"activate" # activate home project
pkg"activate" # activate LOAD_PATH project
@test Base.ACTIVE_PROJECT[] === nothing
# expansion of ~
if !Sys.iswindows()
Expand Down