Downloads:

1,999

Downloads of v 50155.50155:

605

Last Update:

28 Feb 2019

Package Maintainer(s):

Software Author(s):

  • The TeX Users Group (TUG)

Tags:

latex cli sync synctex tex live

Synctex (binaries)

50155.50155 | Updated: 28 Feb 2019

Downloads:

1,999

Downloads of v 50155.50155:

605

Maintainer(s):

Software Author(s):

  • The TeX Users Group (TUG)

Tags:

latex cli sync synctex tex live

Synctex (binaries) 50155.50155

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

To install Synctex (binaries), run the following command from the command line or from PowerShell:

>

To upgrade Synctex (binaries), run the following command from the command line or from PowerShell:

>

To uninstall Synctex (binaries), run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade synctex -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade synctex -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Ensure synctex installed
  win_chocolatey:
    name: synctex
    state: present
    version: 50155.50155
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'synctex' do
  action    :install
  version  '50155.50155'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: synctex,
    Version: 50155.50155,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller synctex
{
   Name     = 'synctex'
   Ensure   = 'Present'
   Version  = '50155.50155'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'synctex':
  provider => 'chocolatey',
  ensure   => '50155.50155',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install synctex version="50155.50155" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved by moderator mkevenaar on 05 Mar 2019.

Description

synctex is a binary from TeX Live distribution that supports syncing between the PDF and the source code in the editor. If your distribution does not have synctex bundled in (such as MiKTeX), install this package and source code syncing should get fixed. Package version relates to the SVN revision of the files in TeX Live repository.

tools\kpathsea631.dll 
md5: E054B39384979A5C47D232C9EB6EB8AC | sha1: C2DA94997EFE6D50B18510C82D94897FDCB6847A | sha256: 6DCF6791A567822B3EB32CD483AF0AF6C3F829ED2367942017BD904523FE3BE4 | sha512: B3BAAE578A7C20639247020726A657078CCDD31B13F368941A66516DBA1E20DE030D0DF03E669B119BDE83DD39BDE2F339AEC0B44FC7F26D257BB639B23DB2CE
tools\LICENSE.txt 
$Id$

COPYING CONDITIONS FOR TeX Live:

To the best of our knowledge, all software in the TeX Live distribution
is freely redistributable (libre, that is, not necessarily gratis),
within the Free Software Foundation's definition and the Debian Free
Software Guidelines.  Where the two conflict, we generally follow the
FSF.  If you find any non-free files included, please contact us
(references given at the end).

That said, TeX Live has neither a single copyright holder nor a single
license covering its entire contents, since it is a collection of many
independent packages.  Therefore, you may copy, modify, and/or
redistribute software from TeX Live only if you comply with the
requirements placed thereon by the owners of the respective packages.

To most easily learn these requirements, we suggest checking the TeX
Catalogue at: http://www.ctan.org/tex-archive/help/Catalogue/ (or any
CTAN mirror).  Of course the legal statements within the packages
themselves are the final authority.

In some cases, TeX Live is distributed with a snapshot of the CTAN
archive, which is entirely independent of and separable from TeX Live
itself.  (The TeX Collection DVD is one example of this.)  Please be
aware that the CTAN snapshot contains many files which are *not* freely
redistributable; see LICENSE.CTAN for more information.


GUIDELINES FOR REDISTRIBUTION:

In general, you may redistribute TeX Live, with or without modification,
for profit or not, according to the usual free software tenets.  Here
are some general guidelines for doing this:

- If you make any changes to the TeX Live distribution or any
package it contains, besides complying with any licensing requirements,
you must prominently mention such changes in your modified distribution
so that users do not take your work for ours, and know to contact you,
not us, in case of questions or problems.  A new top-level file
README.<yourwork> is a good place to describe the general situation.

- Especially (but not necessarily) if changes or additions are made, we
recommend a clearly different title, such as "<your work> DVD, based on
TeX Live YYYY", where YYYY is the year of TeX Live you are using.  This
credits both our work and yours.

- You absolutely may *not* place your own copyright on the entire
distribution, since it is not your work.  Statements such as "all rights
reserved" and "may not be reproduced" are especially reprehensible,
since they are antithetical to the free software principles under which
TeX Live is produced.

- You may use any cover or media label designs that you wish.  Such
packaging and marketing details are not covered by any TeX Live license.

- Finally, we make the following requests (not legal requirements):

a) Acknowledging that TeX Live is developed as a joint effort by all TeX
   user groups, and encouraging the user/reader to join their user group
   of choice, as listed on the web page http://tug.org/usergroups.html.

b) Referencing the TeX Live home page: http://tug.org/texlive/

Such information may be placed on the label of your media, your cover,
and/or in accompanying text (for instance, in the acknowledgements
section of a book).

Finally, although it is again not a requirement, we'd like to invite any
redistributors to make a donation to the project, whether cash or
in-kind, for example via https://www.tug.org/donate/dev.html.  Thanks.


If you have any questions or comments, *please* contact us.  In general,
we appreciate being given the chance to review any TeX Live-related
material in advance of publication, simply to avoid mistakes.  It is
much better to correct text on a CD label or in a book before thousands
of copies are made!

We are also happy to keep anyone planning a publication informed as to
our deadlines and progress.  Just let us know.  However, be aware that
TeX Live is produced entirely by volunteers, and no dates can be
guaranteed.


LICENSING FOR NEW PACKAGES:

Finally, we are often asked what license to use for new work.  To be
considered for inclusion on TeX Live, a package must use a free software
license, such as the LaTeX Project Public License, the GNU General
Public License, the modified BSD license, etc.  (Please use an existing
license instead of making up your own.)  Furthermore, all sources must
be available, including for documentation files.  Please see
http://tug.org/texlive/pkgcontrib.html for more information, and other
considerations.

Thanks for your interest in TeX.

- Karl Berry, for the TeX Live project

------------------------------------------------------------
TeX Live mailing list: http://lists.tug.org/tex-live
TeX Live home page:    http://tug.org/tex-live/

The FSF's free software definition: http://www.gnu.org/philosophy/free-sw.html
Debian Free Software Guidelines:    http://www.debian.org/intro/free
FSF commentary on existing licenses:
  http://www.gnu.org/licenses/license-list.html

LPPL: http://latex-project.org/lppl.html or texmf-dist/doc/latex/base/lppl.txt
LPPL rationale: texmf-dist/doc/latex/base/modguide.pdf
tools\synctex.exe 
md5: 843DC4ED82A948797C17623189836D4D | sha1: AC9622F808702D82038E5665027D9B63A5E46D6A | sha256: D2FEBF2FE42116196385A811C1349BD6F421FA9A403BD87B9D7CBF0A044DAFC2 | sha512: 6E70750D655C8D6BA6CF4ED64A599E2F6E4A92BE864478F218477591DEA1AADF8AE65D0BB2781DE847FA7A411C33859E622CFDBA2AA336E833341A26EBA941CE
tools\VERIFICATION.txt 
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

There are two files in this package: synctex.exe and kpathsea***.dll (*** for version number).
Files are downloaded from the official TeX Live SVN server, from this folder: https://www.tug.org/svn/texlive/trunk/Master/bin/win32/
To verify, download latest revisions of synctex.exe and kpathsea***.dll and ensure they match the files in the package.

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Synctex (binaries) 50155.50155 605 Thursday, February 28, 2019 Approved
Synctex (binaries) 46993.46993 1212 Thursday, March 29, 2018 Approved
Synctex (binaries) 46800.46800 182 Friday, March 16, 2018 Approved

This package has no dependencies.

Discussion for the Synctex (binaries) Package

Ground Rules:

  • This discussion is only about Synctex (binaries) and the Synctex (binaries) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Synctex (binaries), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus