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

Support for readable configuration file #87

Open
hololeap opened this issue Feb 4, 2021 · 3 comments
Open

Support for readable configuration file #87

hololeap opened this issue Feb 4, 2021 · 3 comments
Labels

Comments

@hololeap
Copy link
Member

hololeap commented Feb 4, 2021

I think it would be a good idea going forward to have a readable configuration file for hackport, for instance TOML. I personally like TOML because it was designed to be used for configuration files and there are Haskell libraries for parsing it.

@ezzieyguywuf
Copy link
Contributor

ezzieyguywuf commented Feb 11, 2021

I'm a fan of config-schema, as it is lightweight and gets the job done admiringly.

However, if someone were to submit a solution using TOML (or YAML or whatever) I don't feel strongly enough about it to make a big fuss.

I do agree that some configurability (maybe just an environment variable?) would be helpful.

@pajot
Copy link

pajot commented Mar 2, 2021

+1 for configurability. It would be nice to tell hackport into which overlay it should place the ebuild it generates.

@ezzieyguywuf
Copy link
Contributor

+1 for configurability. It would be nice to tell hackport into which overlay it should place the ebuild it generates.

It's interesting, hackport make-ebuild does allow you to specify the package category (in fact it insists upon it), but hackport merge does not for some reason.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants