matteosecli / matteosecli/latexml-packaging
Improvements in the rules
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Take a look at the `rules` file in the Debian package and see if we can borrow some improvements.
- [ ] Speed up the building process by setting `NOMKTEXLSR=1` as in https://salsa.debian.org/tex-team/latexml/blob/ddea4a5ac82e9db0e7dc28ebb406e86516c2df97/debian/rules#L13. There should be no differences in the final package that is produced, since `dh_installtex`is called anyway.
- [ ] Take a look at how `manual.pdf`is handled in https://salsa.debian.org/tex-team/latexml/blob/ddea4a5ac82e9db0e7dc28ebb406e86516c2df97/debian/rules#L36-39 and https://salsa.debian.org/tex-team/latexml/blob/ddea4a5ac82e9db0e7dc28ebb406e86516c2df97/debian/rules#L49-50 and decide if it's worth the change.
- [ ] We should be already doing https://salsa.debian.org/tex-team/latexml/blob/ddea4a5ac82e9db0e7dc28ebb406e86516c2df97/debian/rules#L46 since we have a dedicated https://github.com/matteosecli/latexml-packaging/blob/master/debian/docs file.
There are no other differences as of 20180813.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing debian/rules with the referenced LaTeX Debian package rules, focusing on NOMKTEXLSR=1 and the manual.pdf handling. Read debian/docs and the corresponding referenced rules lines, then build the package to check whether the proposed changes preserve the final package. Done means the checklist decisions are implemented or documented and packaging behavior is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- debian, latex
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100