<div dir="ltr"><div dir="ltr">I played some time ago with a "brute force" building tool which starts only from the includes of the main source file. It tried to find the packages for these modules using the google search service to search in Hackage, download the package sources from Hackage and added the packages as options to the ghc -ipackage1 ipackage2 command line, recursively. If some error happened I tried with the files of an older version for the package that produced the error, by parsing the GHC errors. It failed at some C import libraries but at this moment it can be switched to build in cabal or stack mode for that package/module.<br></div><div dir="ltr"><br></div><div>I write this just in case this gives some ideas to someone to go along these lines.</div><div><br></div><div>Much of that is what Cabal does anyway, but constrained by the limits imposed by the *.cabal files in the packages. But the machinery is there</div><div>Perhaps Cabal could have a --bruteforce option?</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">El jue, 10 dic 2020 a las 12:25, Ignat Insarov (<<a href="mailto:kindaro@gmail.com">kindaro@gmail.com</a>>) escribió:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"># Do something about Cabal?<br>
<br>
Hello.<br>
<br>
Cabal is the second most used tool in Haskell after GHC. It has many<br>
problems. It may be noticed that there is one and a half developers working on<br>
it. This is clearly not enough to address these problems. I propose that this is<br>
a good place to invest in.<br>
<br>
### Problems I have in mind:<br>
<br>
* Poor communication, lack of open source development process.<br>
<br>
The whole Cabal–Stack schism appears to be an outcome of poor<br>
communication. One of the leading developers of Cabal is even banned from<br>
participation somewhere in Stack circles.[1] Personally, I reported several<br>
issues to Cabal and every single time it resulted in sadness. Observe a<br>
vicious circle: core developers are overworked ⇒ they are being unfriendly ⇒<br>
there are fewer contributors ⇒ core developers are overworked.<br>
<br>
I have no hard evidence but it appears that presently, more people that strive<br>
to improve the Haskell build experience are outside the Cabal cabal than are<br>
inside.<br>
<br>
* User experience is an afterthought.<br>
<br>
Cabal's user experience is horrifying. A collection of complaints is being<br>
compiled elsewhere.[2] There are also bugs being opened to Cabal because of<br>
this, requiring triage and therefore wasting the precious time of the few<br>
overworked developers. Stack is much more friendly — this shows by example<br>
that the user experience problem is not inherent and may be solved.<br>
<br>
It is ordinary to receive output like this:<br>
<br>
```<br>
% cabal run example-executable<br>
Warning: The package list for '<a href="http://hackage.haskell.org" rel="noreferrer" target="_blank">hackage.haskell.org</a>' is 84 days old.<br>
Run 'cabal update' to get the latest list of available packages.<br>
Resolving dependencies...<br>
cabal: Could not resolve dependencies:<br>
[__0] trying: example-0.1.0.6 (user goal)<br>
[__1] next goal: opaleye (dependency of example)<br>
[__1] rejecting: opaleye-0.7.1.0, opaleye-0.7.0.0 (constraint from project<br>
config TODO requires ==0.6.7006.1)<br>
[__1] rejecting: opaleye-0.6.7006.1 (conflict: example => opaleye^>=0.7)<br>
[__1] skipping: opaleye-0.6.7006.0, opaleye-0.6.7005.0, opaleye-0.6.7004.2,<br>
opaleye-0.6.7004.1, opaleye-0.6.7004.0, opaleye-0.6.7003.1,<br>
opaleye-0.6.7003.0, opaleye-0.6.1.0, opaleye-0.6.0.0, opaleye-0.5.4.0,<br>
opaleye-0.5.3.1, opaleye-0.5.3.0, opaleye-0.5.2.2, opaleye-0.5.2.0,<br>
opaleye-0.5.1.1, opaleye-0.5.1.0, opaleye-0.5.0.0, opaleye-0.4.2.0,<br>
opaleye-0.4.1.0, opaleye-0.4.0.0, opaleye-0.3.1.2, opaleye-0.3.1, opaleye-0.3,<br>
opaleye-0.2, opaleye-0.6.7002.0, opaleye-0.6.7001.0, opaleye-0.6.7000.0,<br>
opaleye-0.5.2.1, opaleye-0.3.1.1 (has the same characteristics that caused the<br>
previous version to fail: excluded by constraint '^>=0.7' from example)<br>
[__1] fail (backjumping, conflict set: example, opaleye)<br>
After searching the rest of the dependency tree exhaustively, these were the<br>
goals I've had most trouble fulfilling: opaleye, example<br>
```<br>
<br>
There are so many things that are wrong here. Even a sneaky _«to do»_<br>
remark. If you wonder, in this case the solution is to remove and re-generate<br>
`cabal.project.freeze`.<br>
<br>
Even the name of the program — it is actually _«cabal-install»_ — is<br>
incomprehensible, it should be re-branded to Cabal, which is how everyone<br>
calls it anyway.<br>
<br>
* Features are not being introduced.<br>
<br>
There is no reason for two build tools to exist. The killer feature of Stack —<br>
snapshots — should be supported by Cabal. Possibly Cabal itself should be<br>
refactored and split so that there are separate tools for packaging, version<br>
resolution and human interaction — I do not know. But certainly the way things<br>
are presently is a waste of developer effort and a source of confusion for<br>
everyone.<br>
<br>
### My proposition, in particular.<br>
<br>
* Ask all the people that show compassion to the cause of a great Haskell build<br>
tool to unite and work together on a better Cabal. This includes the<br>
developers of Stack and everyone that expressed unhappiness with the current<br>
state of Cabal. These people should be seen as a blessing, not as an obstacle.<br>
* Put in place a clear process for contributing and decision making, so that it<br>
does not come down to the privileged opinion of one of the core developers.<br>
* Make a model of user experience that Cabal should conform to, and make<br>
conformance a priority. Surely there are among us people that know a thing or<br>
two about user experience — call for them to step forward. Every issue that<br>
stems from misunderstanding, re-assign to the model instead of closing.<br>
* Merge the support of Stackage snapshots into Cabal. Ask the core developers of<br>
Stack to join the effort. Transition from Stack to Cabal should be one well<br>
discoverable command that just works.<br>
<br>
I realize that this letter is largely an opinion piece. You can also see it as<br>
an _«ideal piece»_. Without an ideal, without a vision, we are stuck with the<br>
present. I do not insist that my vision is the best. But the present reality is<br>
not the best vision either. I propose, foremost, that we work and fight for a<br>
better future.<br>
<br>
[1]: <a href="https://github.com/commercialhaskell/stackage/issues/4472" rel="noreferrer" target="_blank">https://github.com/commercialhaskell/stackage/issues/4472</a><br>
[2]: <a href="https://github.com/tomjaguarpaw/tilapia/issues?q=is%3Aissue+is%3Aopen+cabal" rel="noreferrer" target="_blank">https://github.com/tomjaguarpaw/tilapia/issues?q=is%3Aissue+is%3Aopen+cabal</a><br>
_______________________________________________<br>
Haskell-Cafe mailing list<br>
To (un)subscribe, modify options or view archives go to:<br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/haskell-cafe</a><br>
Only members subscribed via the mailman list are allowed to post.</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">Alberto.</div>