Comments (2)
Ideally there would be a flag --allow-deprecated
(and a cabal.project
option allow-deprecated
), similar to --allow-{newer,older}
, which explicitly allows cabal
to use deprecated package version in the build plan. Packages which are deprecated are deprecated for a reason, and it's rather surprising when they are picked by cabal constraint solver.
This actually gives control to the end user, and to a package maintainer. Maintainers no longer will need to use base < 0
trick on hackage
, which seems like a hack around missing --allow-deprecated
option.
from cabal.
This is for deprecated versions isn't it and not for whole package deprecations?
Deprecating a version adds a range which excludes just that version. All of this information is collected in the preferred-versions file that's included in the index tarball. [maintainers: edit]
If all the available versions of a package are non-preferred or deprecated, cabal-install will treat this the same as if none of them are. This feature doesn't affect whether or not to install a package, only for selecting versions after a given package has decided to be installed. Entire-package deprecation is also available, but it's separate from preferred versions.
SOURCE: https://hackage.haskell.org/package/binary/preferred
from cabal.
Related Issues (20)
- pkgsUseSharedLibrary logic is incorrect HOT 1
- cabal haddock-project suggests --haddock-all but then rejects it HOT 1
- Cabal-3.12.0.0 passes include dirs to GHC in a new order HOT 6
- build-tool-depends in Cabal regresses ghc ability to build from source distribution HOT 5
- Cabal external command requires typing Return to exit HOT 1
- Support monitoring directory recursive globs
- cabal init fails if git is not installed HOT 5
- Failure to find a program produces an incomprehensible error
- Encountered possible bug during building rpki-prover HOT 14
- Using Setup.hs build --with-ghc looses configure --ghc-option HOT 1
- Conditions don't work with flags HOT 2
- Are we validating `ghc-options` in `.cabal` files? HOT 4
- Do not pass environment variables to `happy`/`alex`, or at least allow a way to filter HOT 2
- Is the `CabalParsing` class necessary? HOT 2
- Changelog for Cabal 3.12 is missing mention of error codes
- Amend non-reinstallable packages list HOT 6
- "Use of GHC's environment variable GHC_PACKAGE_PATH is incompatible with Cabal" when running `Setup.hs test` should be a warning, not an error HOT 4
- Remember "Choose a language for" choice on `cabal init` HOT 3
- Favour non-preferred versions over deprecated versions
- [RFC] Revive cabal sandboxes (UX) HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cabal.