Date: Wed, 02 Apr 2025 11:28:32 +0000 From: bugzilla-noreply@freebsd.org To: haskell@FreeBSD.org Subject: [Bug 285823] devel/hs-haskell-language-server: update 2.9.0.1 => 2.10.0.0 Message-ID: <bug-285823-16154-iQ4Oh9ym00@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-285823-16154@https.bugs.freebsd.org/bugzilla/> References: <bug-285823-16154@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D285823 --- Comment #5 from =C3=84lven <alster@vinterdalen.se> --- (In reply to Gleb Popov from comment #4) > I think we should follow upstream as much as possible in Ports. Also agree. That's why I proposed switch MASTER_SITES - to follow upstream = by using upstream distfile. The question is only, what is actually upstream? 1) downloads.haskell.org is likely the most official one, as a direct subdo= main of the haskell.org itself. - https://downloads.haskell.org/~hls/haskell-language-server-2.10.0.0/haskell= -language-server-2.10.0.0-src.tar.gz 2) hackage.haskell.org may be the main one as well as another direct subdom= ain of the haskell.org, especially for hackage packages, and it have somewhat better DISTNAME, without -src suffix. May you like it more? - https://hackage.haskell.org/package/haskell-language-server-2.10.0.0/haskel= l-language-server-2.10.0.0.tar.gz After all, I see this as maintainer duty to not to put all the eggs in one basket, but care of diversity and stability of package ecosystems, even if upstream doesn't. --=20 You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-285823-16154-iQ4Oh9ym00>