Skip to content
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

hledger and its many, many dependencies #104

Merged
merged 3 commits into from Aug 2, 2018

Conversation

Projects
None yet
2 participants
@solresol
Copy link
Contributor

solresol commented Jul 29, 2018

hledger is a text-based accounting application written in Haskell.

It has a few user interface options. This pull includes hledger-ui, which is a curses-based UI. hledger-web is not, as it has dependencies on some weird stuff not yet ported to *BSD; as it is the only part of the hledger package that ever calls listen() it's the one most likely to have a security problem. Everything else runs unprivileged as the invoking user and writes plain text files which are writable to the user anyway.

The rest of this quite large pull request are all the dependencies needed for hledger to compile. The community of Haskell developers on OpenBSD will be quite excited, as this covers a large number of the libraries that they would otherwise bring in via stack or cabal.

(By the way, accounting here means debits and credits and preparing financial statements -- the kinds of things accountants and book-keepers work with).

solresol added some commits Jul 29, 2018

@ibara

This comment has been minimized.

Copy link
Collaborator

ibara commented Jul 29, 2018

First of all, wow. Did you do this all yourself?

Now for the nitty-gritty:
Could you add a TODO file in the main hledger port with a list of all the dependencies and perhaps a plan of action for the order in which ports need to go in. That way ports can be prioritized and we can keep track of submissions, what has already been committed, etc.

@solresol

This comment has been minimized.

Copy link
Contributor Author

solresol commented Jul 29, 2018

@ibara -- mostly subcontracted. I needed hledger and this was the most efficient way to get it. But I'll aim to be the maintainer of it since it's the itch I need to keep scratched.

For the TODO file, essentially we're looking for a directed graph of dependencies, so that we can see which are the leaf nodes, is that right? e.g. hledger depends on hs-ansi-terminal, which depends on hs-colour. hs-colour depends on nothing, so we should prioritise hs-colour.

I'm not in any hurry, have a day job and I don't want to put a lot of burden on anyone, so I was thinking of aiming for one package per week (probably each Sunday) for the next year or so.

@ibara

This comment has been minimized.

Copy link
Collaborator

ibara commented Jul 29, 2018

Yes, that's exactly what I'm looking for from the TODO.

Hopefully we can move faster than one package per week :)

@ibara

This comment has been minimized.

Copy link
Collaborator

ibara commented Aug 2, 2018

Thanks. I've merged this. Now comes the fun part of getting all of this committed to CVS :)

@ibara ibara merged commit fdc3ad3 into jasperla:master Aug 2, 2018

@ibara

This comment has been minimized.

Copy link
Collaborator

ibara commented Aug 21, 2018

@solresol I'm sorry I don't have another way of contacting you. Whenever you're ready, please start sending these to the ports@ mailing list to be incorporated into CVS. I'd hate to see all this work stagnate here.

@solresol

This comment has been minimized.

Copy link
Contributor Author

solresol commented Aug 21, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.