Windows shell opam init
#16
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7c28973
to
0773da5
Compare
8d69cef
to
138fc40
Compare
138fc40
to
9c8f762
Compare
d6b2f1c
to
95c4f13
Compare
3bc81d9
to
7946515
Compare
c5a1b0e
to
8fa3ace
Compare
8fa3ace
to
6c70f9f
Compare
Co-authored-by: David Allsopp <[email protected]>
The script only scanned src_ext/Makefile.sources. Trivial refactoring to scan and update packages in both files.
Fish integration: nitpicking
Upgrade the vendored dune to 3.14.0 and other packages to their latest release
:= and =: now ensure that an empty directory empty is always introduced then all the append operators ensure that an empty directory entry is maintained (see env.test changes).
Fixes to reversal of environment updates
There are two problems we can encounter with symlinks on Windows: - The user cannot create native symlinks (Developer Mode is not enabled) - At the point that the symlink is created, the file it refers to does not exist In this instance, Cygwin's tar falls back to its internal mechanisms, which can't be read by opam and cause issues when copying directories, etc. This commit mitigates the directory copy by displaying a warning and fixes the deletion of the directory by deleting the file anyway.
Mitigate copying/deletion of unrecognised symlinks
Update shell/install.sh for opam 2.1.6
Release script fixes and improvements
Fix opamfile package var typo
Tweak incorrect case in `--cygwin-extra-packages`
The last-env files are now stored in `~/.opam/.last-env` dir.
Move last-env `OPAM_LAST_ENV` files outside the switch
The warnings emitted for guarded-dependency and no-dependency-guarded are not strictly necessary as they are protected by a filter which checks :installed (:installed at present never triggers warning 41). The warning for no-dependency-unguarded is unequivocally correct.
Warning 41 is never triggered for the use of package:installed. Extend
this so that the warning is not triggered for any uses of package:foo
_underneath_ package:installed, i.e.
"%{package:foo}% {package:installed}
can no longer cause warning 41 on package.
The previous change means that a variable will definitely not be expanded unless the package has been installed. However, there is a timing issue which is not desirable - there is no guarantee that if either no-dependency-guarded or no-dependency-installed-only have been installed that they will be installed before or after the current package. This instability is not desirable, either. The check is therefore enhanced slightly so that foo:installed can only be used if depends or depopts in some way mentions the package (rather than doing a full tautology check on depends for whether foo is installed).
UTF-8 paged --help on Windows
Relax warning 41 for package variables guarded by a :installed filter
If the environment file is missing, recomputing it can take a noticeable amount of time which delays every single return of the prompt when the env_hook is enabled. The use of atomic write on the environment file instead of a lock means that the environment hooks can store the generated environment file if it's missing, or needs regenerating.
On Windows, files older than the system uptime are automatically pruned. On Unix, the original solution was using /tmp, but we could bind something similar...
Returns %ProgramData%\opam now
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.