Skip to content

fix: Deadlink in README.md #15

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.

Sign up for GitHub

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

Merged
felixonmars merged 1 commit into from
Jun 18, 2026
Merged

fix: Deadlink in README.md #15

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@
In distribution packaging, sometimes we need modify the version range of dependencies. Usually, this can be done by some *nix text processing utilities, such as awk, sed, etc.
However, these tools process cabal files as plain text, not considering the semantics. Thus, it might be pesky or elusive to conver the entire cases.
`uusi` has almost no extra dependencies, so it's safe to introduce `uusi` as build-depends of the target, which packagers can use to manipulate target's dependencies.
Currently, `uusi` works in Arch Linux packaging, and you may find out that it has been [required by](https://www.archlinux.org/packages/community/x86_64/uusi/) many haskell packages.
Currently, `uusi` works in Arch Linux packaging, and you may find out that it has been [required by](https://www.archlinux.org/packages/extra/x86_64/uusi/) many haskell packages.
In most cases, it is used to loose the version constraint of a dependency when building a package, because the dependent haskell package provided by system may be too new to fit the constraints,
whereas this package can be built against the newer dependency successfully.

Expand Down