nico.schloemer at gmail.com
Fri Oct 13 12:03:54 CEST 2017
> You mean an API to get betterbib into our subversion server? No, that is not
That's what I meant.
Whenever I publish a new version of betterbib, I use a simple Makefile to
push the data upstream. This works
* for releases on GitHub  (via `git tag v1.2.3 && git push --tags`) as
* for releases on pypi  (via `python setup.py bdist_wheel --universal
&& gpg --detach-sign -a dist/* && twine upload dist/*`).
This makes releasing new versions really easy for me. Having to manually
open a browser, navigate to a website, copy-and-pasting some information
from the package into input fields, and clicking a submit button would be a
step back, and I can already see myself forget doing it.
Perhaps this is a feature you'd like to add sometime in the future.
On Fri, Oct 13, 2017 at 11:47 AM Norbert Preining <norbert at preining.info>
> Hi Nico,
> > Is it possible to update the package via an API or would I have to go to
> > the website manually each time I release a new version?
> You mean an API to get betterbib into our subversion server? No, that is
> not possible.
> And yes, every update you want to get into TeX Live needs to go through
> This is how everyone is doing it.
> OTOH, if you meant that the API is used to update the actual installation
> the *user* computer, then well, in principle you *could* try to do it, but
> in many cases the user running the script will not have *write* permissions
> to the location where betterbib is installed. (Unix root/user, Win admin
> So I think this is not a good idea.
> All the best
> PREINING Norbert http://www.preining.info
> Accelia Inc. + JAIST + TeX Live + Debian Developer
> GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tex-live