Skip to content

cabal list should make it clear that a package is old/deprecated #2163

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

Open
Fuuzetsu opened this issue Oct 14, 2014 · 3 comments
Open

cabal list should make it clear that a package is old/deprecated #2163

Fuuzetsu opened this issue Oct 14, 2014 · 3 comments
Labels
cabal-install: other re: deprecated packages and versions Concerning handling of packages and versions deprecated on the package repository type: enhancement

Comments

@Fuuzetsu
Copy link
Member

So we just had someone in #yi install a deprecated package (marked as deprecated) from 2008:

<alanz> cabal list yi gives the following
<alanz> * yi-gtk
<alanz>     Synopsis: The Haskell-Scriptable Editor, helper package
<alanz>     Default available version: 0.3
<alanz>     Installed versions: 0.3
<alanz>     Homepage: http://haskell.org/haskellwiki/Yi
<alanz>     License:  GPL
<alanz> Nothing about deprecation, or date

It seems to me that cabal should make at least some attempt to communicate that this may in fact not be the right package to install.

@ezyang
Copy link
Contributor

ezyang commented Oct 16, 2014

Should we hide the deprecated packages by default? That seems like the most friendly thing to me.

@23Skidoo
Copy link
Member

Main problem here seems to be that the information about whether the package is deprecated is not available inside D.C.List. In general, deprecating a package on Hackage currently has no effect on cabal-install behaviour.

To fix this we need to modify both cabal-install and hackage-server:

  1. Hackage server should serve a file containing a list of deprecated packages inside the index tarball (similar to preferred-versions).
  2. In cabal-install code there should be a flag inside the SourcePackage record specifying whether a package is deprecated.

@ttuegel ttuegel added this to the cabal-install-1.24 milestone Apr 24, 2015
@23Skidoo 23Skidoo modified the milestones: cabal-install 1.24, cabal-install 1.26 Feb 21, 2016
@ezyang ezyang modified the milestone: cabal-install 2.0 Sep 6, 2016
@jneira
Copy link
Member

jneira commented Mar 24, 2022

re #1518 where an user ask for a warning when building a deprecated package, so other way, more direct of communicate the fact
it would need some of the changed described above

@ulysses4ever ulysses4ever added the re: deprecated packages and versions Concerning handling of packages and versions deprecated on the package repository label Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cabal-install: other re: deprecated packages and versions Concerning handling of packages and versions deprecated on the package repository type: enhancement
Projects
None yet
Development

No branches or pull requests

6 participants