Package Details: sublime-text-2 2.0.2-2

Git Clone URL: (read-only, click to copy)
Package Base: sublime-text-2
Description: Sophisticated text editor for code, html and prose (legacy version)
Upstream URL:
Licenses: custom: commercial
Submitter: SunRed
Maintainer: carstene1ns
Last Packager: SunRed
Votes: 544
Popularity: 0.000028
First Submitted: 2022-11-15 17:00 (UTC)
Last Updated: 2022-11-15 17:00 (UTC)

Latest Comments

1 2 3 4 5 6 .. 16 Next › Last »

carstene1ns commented on 2021-05-13 13:05 (UTC)

You are free to create the renamed package and send a merge request. Please stop flagging and being rude.

NullRoute commented on 2021-05-01 05:19 (UTC)

I agree with relrel, it should be renamed to "sublime-text-2" and also should NOT force users to remove "sublime-text-3" it should be installed to "subl2" and NOT as "subl" which breaks "sublime-text-3" install. This two packages can easierly be run side by side and there absolutely no reason to force users one or the other. Some of us like to use both, especially if we paid for the license.

relrel commented on 2020-10-16 14:41 (UTC)

This package should be renamed to sublime-text-2, to be consistent with sublime-text-3.

TheChickenMan commented on 2017-09-19 13:50 (UTC)

I'm not sure I really like the idea of adding additional repositories to pacman. I like keeping my official packages only with pacman and my AUR stuff separate.

davidgxxl commented on 2017-09-18 21:11 (UTC)

I just update this today(3144) and when try open sublime text I got "enter license key" dialog... I dont know if there any issue with that version, but now I'm using the sublime text stable official reposity for pacman Regards.

carstene1ns commented on 2017-09-14 14:04 (UTC)

Yes, my plan is to reupload this package as sublime-text2 and file a merge request. However, the recommended way to get sublime text 3 is via the custom pacman repo. Therefore my idea is to provide a package "sublime-text-repository" or something that adds it, so pacman will manage the updates. I have no intention to block this package base, so current dev/nighly package maintainer (@sender) may upload their sublime-text (version 3) here.

jkwill87 commented on 2017-09-13 22:09 (UTC)

My $0.02: sublime-text should be updated to Sublime Text 3. Modernity is one of Arch's core principles, and as such sublime-text should reflect the latest upstream version. Package naming should follow suit to python, another package with a divisive update between 2 to 3, where the package for Sublime Text 2 could just moved over to something like sublime-text2 or sublime-text-2.

nathan-osman commented on 2017-09-13 16:42 (UTC)

Now that Sublime Text 3 is out (, will this package be upgraded?