Skip to content

Add the pgfopts package#63

Merged
patbro merged 1 commit intoProdriveTechnologies:masterfrom
Kernald:pgfopts
Dec 17, 2021
Merged

Add the pgfopts package#63
patbro merged 1 commit intoProdriveTechnologies:masterfrom
Kernald:pgfopts

Conversation

@Kernald
Copy link
Copy Markdown
Collaborator

@Kernald Kernald commented Aug 3, 2021

No description provided.

Setting up a test for this package seems extremely convoluted, the
current minimalistic test just checks that all the dependencies are
there, as is done for pgfcore.
@patbro
Copy link
Copy Markdown
Member

patbro commented Dec 14, 2021

I took a brief look at https://mirror.lyrahosting.com/CTAN/macros/latex/contrib/pgfopts/pgfopts.dtx but it doesn't seem easy to add a proper test. Or is it?

I would rather not merge this PR without a proper test. Then probably no test will be made at all.

@Kernald
Copy link
Copy Markdown
Collaborator Author

Kernald commented Dec 15, 2021

I don't know of an easy way to test this either. I'm not using it directly, I'm just trying to get it in as a transitive dependency of another package I'm looking to use.

@patbro
Copy link
Copy Markdown
Member

patbro commented Dec 15, 2021

Wouldn't it then be more logical to add @texlive_texmf__texmf-dist__tex__latex__pgfopts to your package locally using a patch instead?

@Kernald
Copy link
Copy Markdown
Collaborator Author

Kernald commented Dec 15, 2021

I think the situation is the exact same as #67 - adding a new package isn't exactly trivial, especially when dependencies include fonts etc. Ultimately, it's the same discussion we had in #58 (comment). I totally understand that you don't want to maintain additional packages that you're not using though - I think it would be worth having a clear decision written somewhere on whether you want to accept third party contributions of new packages or not. It's a bit confusing having a bunch of packages defined in this repo, and then some PRs closed because you're not using them.

(With that said, I'm well aware that this specific PR lacks tests, and I don't have an obvious solution to this.)

@patbro
Copy link
Copy Markdown
Member

patbro commented Dec 17, 2021

To be honest, making sure people can use bazel-latex in its full glory is more important than the additional work of reviewing all PRs and merging them. Until I have a proper solution to this, it's best to just merge those PRs. I will add a CONTRIBUTING.md file as well.

Hopefully, the number of packages doesn't become too big, which would cause the CI to take way too long.

@patbro patbro merged commit b061079 into ProdriveTechnologies:master Dec 17, 2021
@Kernald Kernald deleted the pgfopts branch December 17, 2021 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants