-
Notifications
You must be signed in to change notification settings - Fork 4
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
Register file-io as a GHC boot library #22
Comments
It can. There's no formal process for it. If a boot package adds a new dependency, then GHC HQ has to include that new depednency when bundling it. I'd go so far to say this isn't even core lib maintainers business. GHC just chooses to ship with libraries. It's a redistribution effort. Of course we have to be mindful about e.g. circular dependencies etc. |
FWIW, GHC has no objection to adding this dependency as a boot library. |
Given that Cabal does not like reinstalling boot libraries, we'd better be sure that One option is to make a release of |
I'm not sure that gains us much, because that's just directory package using a small part of file-io. haskell/cabal#9669 needs to be solved, because it is also a security hazard. I can't fix bugs in a timely fashion as a core library maintainer. If we were to use a Cabal flag, then:
|
I could also provide an |
@Bodigrim @hasufell @Rufflewind I have opened a GHC issue in order to discuss adding a new boot library (file-io). Please contribute there with your opinions. |
Ownership has been given to CLC and I moved the repo to haskell. Everything else can be handled on GHC side. |
Can
file-io
be included in the GHC boot libraries so thatdirectory
can depend on it?This is motivated by haskell/directory#177 (comment) .
@Bodigrim @bgamari
The text was updated successfully, but these errors were encountered: