Package Details: sublime-text-dev 3.3211-1

Git Clone URL: https://aur.archlinux.org/sublime-text-dev.git (read-only, click to copy)
Package Base: sublime-text-dev
Description: Sophisticated text editor for code, html and prose - dev build
Upstream URL: http://www.sublimetext.com/3
Licenses: custom
Conflicts: sublime-text-nightly
Provides: sublime-text-nightly
Submitter: realitygaps
Maintainer: sender
Last Packager: sender
Votes: 507
Popularity: 2.44
First Submitted: 2011-11-10 18:32
Last Updated: 2019-10-01 09:31

Pinned Comments

sender commented on 2017-06-04 15:31

Since 26 May 2017 Sublime Text 3 is available via the dedicated pacman repo provided by the author. From now on this is the recommended way to install ST3 on Arch Linux.

Package sublime-text-dev is replaced by repo 'stable'.
Package sublime-text-nightly is replaced by repo 'dev'.

See: https://www.sublimetext.com/docs/3/linux_repositories.html#pacman

sender commented on 2016-02-17 08:37

There seems to be a lot of confusion about the ST packages. This is because the author switched names for branches. Packages:

Sublime Text 3 Beta
- package: sublime-text-dev
- Upstream: www.sublimetext.com/3

Sublime Text 3 Dev (used to be called nightly)
- package: sublime-text-nightly
- upstream: www.sublimetext.com/3dev
- NOTE: for registered users only

If you want the absolute latest get *sublime-text-nightly*. Note that you have to be licensed to use this!

Latest Comments

« First ‹ Previous ... 2 3 4 5 6 7 8 9 10 11 12 ... Next › Last »

sender commented on 2016-04-17 12:26

@nmstoker It's a very unfortunate situation. No idea on the timing. You can raise this issue upstream. BTW nothing wrong with moving to the -nightly ;)

nmstoker commented on 2016-04-16 20:41

Hi @sender - any idea on the timing that Beta might move to build 3109 (or above)? The SSL error is causing me a few issues, but I suspect I probably shouldn't just switch to Dev (-nightly) especially if it's coming any time soon.

gadicc commented on 2016-03-30 16:36

thanks @sender! and for your ongoing maintenance of this package.

sender commented on 2016-03-30 15:35

@gadicc and others: the ssl-linux issue has been resolved in ST3 build 3109 (available via the nightly channel: https://aur.archlinux.org/packages/sublime-text-nightly). Thanks Esgariot.

gadicc commented on 2016-03-12 07:11

For me, some plugins (that depend on SSL) stopped working on updating from openssl 1.0.2.f-1 -> 1.0.2.g-3.

No error messages outside the console, but there I found messages about being unable to import _ssl, and upon manually adding the "Linux SSL" package (in sublime), errors about OPENSSL_1.0.0 not being defined in libssl1.0.0.

The quick fix was to downgrade with `pacman -U /var/cache/pacman/pkg/openssl-1.0.2.f-1-x86_64.pkg.tar.xz`, reload sublime, and everything worked again. Since this was a minor update, I imagine existing libraries should still work? Maybe someone who understands OpenSSL better can open an appropriate bug report, if relevant.

sender commented on 2016-02-17 08:37

There seems to be a lot of confusion about the ST packages. This is because the author switched names for branches. Packages:

Sublime Text 3 Beta
- package: sublime-text-dev
- Upstream: www.sublimetext.com/3

Sublime Text 3 Dev (used to be called nightly)
- package: sublime-text-nightly
- upstream: www.sublimetext.com/3dev
- NOTE: for registered users only

If you want the absolute latest get *sublime-text-nightly*. Note that you have to be licensed to use this!

sender commented on 2016-02-09 09:12

Updated to 3103! First movement in the (original) dev branch since March 2015. For intermediate updates see package https://aur.archlinux.org/packages/sublime-text-nightly. Note that this version is only available to licensed users only.

GomZik commented on 2016-02-09 08:27

Hi, here is my patch for new build

http://pastebin.com/PmN1ZU2B

lukasw commented on 2016-02-09 03:44

Build 3103 has just been released, see https://www.sublimetext.com/blog/articles/sublime-text-3-build-3103

zerophase commented on 2016-01-23 06:05

I think it's that the provides and conflicts are mixed up for the two sublime-text-nightly and dev.

sublime-text-nightly:
Conflicts: sublime-text-dev
Provides: sublime-text-dev

sublime-text-dev:
Conflicts: sublime-text-nightly
Provides: sublime-text-nightly