From: Chocimier <Chocimier@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: Texlive update
Date: Tue, 19 Jan 2021 19:46:55 +0100 [thread overview]
Message-ID: <20210119184655.i56TuYC8J2J7YWtSiUL4-PpKQ05fQkcuCkZYjYDWcek@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27569@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
There's a merged pull request on the void-packages repository
Texlive update
https://github.com/void-linux/void-packages/pull/27569
Description:
This is the first texlive update (well, texmf packge) update ever.
The metapackages have been updated to pull in the new versions of the packages.
The build_style do_check needs some further fixing. It was flawed on updates because it checked against every single version of the package in repositories. I fixed that in the first commit. However, there is another problem. All of the packages have to first be built and then check run for each package, otherwise it is checking against the outdated information on the other packages.
IMO, the best way to solve this would be to restrict the search to only the repository where the binpkgs are being generated. This means that some checks will be missed in CI but it will pass, and when it is updated on a local machine we can do the two pass:
1. `./xbps-src pkg texlive-blah` for each package
2. `./xbps-src check texlive-blah` for each package
Which is required anyway right now to check and for it to succeed.
@Chocimier thoughts on this above proposal, as you originally wrote the do_check.
prev parent reply other threads:[~2021-01-19 18:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 0:43 [PR PATCH] " fosslinux
2020-12-31 11:10 ` Chocimier
2020-12-31 23:34 ` fosslinux
2020-12-31 23:58 ` [PR PATCH] [Updated] " fosslinux
2021-01-04 19:36 ` Chocimier
2021-01-18 20:47 ` Chocimier
2021-01-19 0:06 ` fosslinux
2021-01-19 0:07 ` fosslinux
2021-01-19 0:07 ` fosslinux
2021-01-19 18:46 ` Chocimier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210119184655.i56TuYC8J2J7YWtSiUL4-PpKQ05fQkcuCkZYjYDWcek@z \
--to=chocimier@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).