Package Details: brackets 1.6-1

Git Clone URL: https://aur.archlinux.org/brackets.git (read-only)
Package Base: brackets
Description: An open source code editor for the web, written in JavaScript, HTML and CSS. Stable git Tags.
Upstream URL: http://brackets.io
Licenses: MIT
Conflicts: brackets-bin, brackets-git
Submitter: 4javier
Maintainer: 4javier
Last Packager: 4javier
Votes: 70
Popularity: 5.779323
First Submitted: 2013-12-05 11:44
Last Updated: 2016-02-02 21:05

Dependencies (15)

Required by (0)

Sources (2)

Latest Comments

4javier commented on 2016-02-02 21:07

Been busy last months. Totally forgot this pkgbuild.

tjaart commented on 2016-02-02 20:39

Been out of date for a really long time now. 1.6 is already out.
Any chance of getting an update?

Moter8 commented on 2015-08-16 10:59

@4javier, 1.4 is out :)

4javier commented on 2015-05-29 20:04

@triceratops1
why did you flag the package as out of date? I cannot find any new release on brackets site.

4javier commented on 2015-05-14 00:57

I'll change the dep in next brackets release.

FSMaxB commented on 2015-05-14 00:15

Please change the dependency libudev.so.0 to libudev0, because the former is a really really dirty hack (just a symlink) whereas the latter actually builds the old libudev.

4javier commented on 2015-05-09 15:53

pacman -Ss npm
community/npm 2.9.0-1
A package manager for javascript

Update your dbs. Try to change mirrors.

It will not work when you will update nodejs to 0.12.2-4, that will delete the npm files installed by previous versions.

4javier commented on 2015-05-09 15:51

pacman -Ss npm
community/npm 2.9.0-1
A package manager for javascript

Update your dbs. Try to change mirrors.

JohnBlood commented on 2015-05-09 15:31

I tried to update but it could not install npm. When I search Pacman, I can't find any packages named npm. I already have npm 2.9.1 installed. Why won't it work?

4javier commented on 2015-05-09 10:42

Added npm as dependency, due to the fact that nodejs does not ship npm anymore from 0.12.2-4

4javier commented on 2015-04-15 00:39

Do you really think I don't know which are brackets releases?
I was just waiting for jasonsanjose's branch to be merged to master, given that there are just few bugs still open.
Anyway, tomorrow I think I'll release 1.2 pkgbuild.

alexandernst commented on 2015-04-14 18:28

@4javier You couldn't be more confused. STABLE doesn't mean master. It means the latest stable tag (which right now is 1.2).

Also, brackets download page offers 1.2 as stable, instead of offering 1.0

Last but not least important, check https://github.com/adobe/brackets/wiki#releases

4javier commented on 2015-04-14 18:18

It's not fear, but simple coherence.
As I stated in PKGBUILD description, this is a build based on STABLE git tags. It's obvious that it refers to MASTER branch.
They built 1.2 deb against the older CEF version.
If everybody really can't wait master to be fixed, tomorrow I'll release a new version checking out the other branch.

alexandernst commented on 2015-04-14 18:03

@3javier I can't really see your point. Version 1.2 was already tagged almost a month ago. It's stable. And it's packaged for Linux.

Are you scared from using branches?

4javier commented on 2015-04-14 17:52

@AbrarSyed
Please, read 5 comments below.

AbrarSyed commented on 2015-04-14 16:06

Why so out of date? Brackets 1.2 has been out for ages...

4javier commented on 2015-04-07 11:22

I think it's a yaourt problem. Anyway you could try:
- to clean yaourt cache, if your /tmp is non-volatile or if that's not first bulding try of the package for that session
or
- clean npm cache with "npm cache clean"

cmorgenstern commented on 2015-04-07 11:15

Here is the error I get after the build starts. I do use yaourt as an AUR wrapper.

==> Starting build()...

> Brackets-Shell@1.0.0-0 preinstall /tmp/yaourt-tmp-user/aur-brackets/src/brackets-shell
> bash -c 'mv appshell.gyp .appshell.gyp'

npm WARN deprecated guid@0.0.10: Please use node-uuid instead. It is much better.
npm WARN locking Error: EACCES, open '/home/user/.npm/_locks/grunt-contrib-clean-6eb37e914eaa809a.lock'
npm WARN locking at Error (native)
npm WARN locking /home/user/.npm/_locks/grunt-contrib-clean-6eb37e914eaa809a.lock failed { [Error: EACCES, open '/home/user/.npm/_locks/grunt-contrib-clean-6eb37e914eaa809a.lock']
npm WARN locking errno: -13,
npm WARN locking code: 'EACCES',
npm WARN locking path: '/home/user/.npm/_locks/grunt-contrib-clean-6eb37e914eaa809a.lock' }
npm ERR! Linux 3.19.3-1-ARCH
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v0.12.2
npm ERR! npm v2.7.5

npm ERR! Attempt to unlock /tmp/yaourt-tmp-user/aur-brackets/src/brackets-shell/node_modules/grunt-contrib-clean, which hasn't been locked
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
----------------------------------------------------

4javier commented on 2015-04-07 10:48

npm install is executed in a fakeroot environment: why should you have root permissions? Post the exact error.
Are you using an AUR wrapper?

4javier commented on 2015-04-07 10:48

npm install is executed in a fakeroot environmento: why should you have root permissions? Post the exact error.
Are you using an AUR wrapper?

cmorgenstern commented on 2015-04-07 07:10

Did anyone encounter difficulty building the package because npm could not install the appropriate components?

I solved it rather crudely by editing the PKGBUILD to force the build to ask for sudo permission for each step. If anyone else experienced a similar problem or has a better solution to circumventing this error, please let me know.

4javier commented on 2015-03-28 13:08

@CorEnsute
Fixed. gyp-svn has been merged with gyp-git on AUR.

@everybody
please, don't flag this pkgbuild as out-of-date. 1.0 version is the last tag building on linux from master branch. To build 1.1 or 1.2 I should checkout a different branch, and I prefer to not do that. Thanks.

CorEnsute commented on 2015-03-28 10:01

Can't be built any more as gyp-svn is not available any more in aur.

4javier commented on 2015-01-13 15:20

Please always read previous comments before posting.
https://github.com/adobe/brackets/issues/10231

Paurf3 commented on 2015-01-13 13:29

Version 1.1 is out!

4javier commented on 2015-01-05 11:19

As replied on a previous comment, there's already p7zip as makedepend.

Siper commented on 2015-01-03 19:37

Add unzip package to dependecies, it's missing.

4javier commented on 2014-12-19 18:48

I will not use --depth 1 because this would break submodule update.
To use it just in cloning, i should go back to the old GIT pkgbuild guidelines, losing many of the automatisms of makepkg.
I don't like this, but it seems that devs disagree with a patch proposal in this way https://bugs.archlinux.org/task/34677

Anyway, only first makepkg will download the whole repo, further pkg update will only fetch the repo.

I didn't update to 1.1 yet because of a build error https://github.com/adobe/brackets/issues/10231

4javier commented on 2014-12-19 18:43

I will not use --depth 1 because this would break submodule update.
To use it just in cloning, i should go back to the old GIT pkgbuild guidelines, losing many of the automatisms of makepkg.
I don't like this, but it seems that devs disagree with a patch proposal in this way https://bugs.archlinux.org/task/34677

Anyway, only first makepkg will download the whole repo, further pkg update will only fetch the repo.

4javier commented on 2014-11-25 23:52

I was sure I was already doing that. :/
Next release will have --depth 1.

kiz commented on 2014-11-25 23:15

please use --depth 1 when cloning from repository

4javier commented on 2014-11-05 11:29

I'll wait for bracket-shell 1.0 to be released too to update the package.

4javier commented on 2014-11-05 10:55

That's not a solution: it's an old ticket where he simply tells to symlink libudev. This was the hack we used until some time ago, but it took problems to x86_64 users.

jleclanche commented on 2014-11-05 07:54

According to https://github.com/adobe/brackets/issues/4720 you don't need libudev.so.0 anymore

4javier commented on 2014-10-11 12:12



Updated, thanks.
Notice that in this version I deleted nodejs-grunt-cli from makedepends, and let npm download and install grunt-cli. Build() function has been modified to look in the correct directory for the fresh grunt-cli binary.
One less AUR dependency, and a solution for the problem BunBum encountered.

4javier commented on 2014-10-11 12:11

Updated, thanks.
Notice that in this version I deleted nodejs-grunt-cli from makedepends, and let npm download and install grunt-cli. Build() function has been modified to look in the correct directory for the fresh grunt-cli binary.
One less AUR dependency, and a solution for the problem BumBum encountered.

ingorichter commented on 2014-10-10 20:56

@4javier Bracket shell 0.44 is available from https://github.com/adobe/brackets-shell/tree/release-0.44

4javier commented on 2014-10-07 08:51

I know this package is out of date. I'm waiting brackets-shell 0.44 to be released.

4javier commented on 2014-09-16 08:34

@BunBum
If you want to contribute, this is the thread where we're discussing about this.

BunBum commented on 2014-09-12 05:32

I understand your problem. Hmmm... Unfortunately I don't know what the Arch guidelines say about packages from other package managers like npm, PyPi and so on.

4javier commented on 2014-09-11 19:49

I'm still undecided about the solution: remove dependency and add npm install -g grunt-cli to build() function, or leave everything as is.
I'd like to know which are Arch guidelines about nodejs packages.

BunBum commented on 2014-09-11 16:28

I did install grunt-cli through "npm install -g grunt-cli" because I install all node.js packages via npm. This way I keep the npm packages seperated from the operating system packages. The same way I do this with Python PyPi Packages, bower dependencies, Ruby Gem and so on.

4javier commented on 2014-09-11 11:27

I'm not a NodeJS expert, and I think I should choice if make this package depend on AUR packaged version of njs tools, or let the pkgbuild run "npm install xxx".
Why did you have grunt-cli already installed through npm-install?

BunBum commented on 2014-09-11 07:12

nodejs-grunt-cli fails to install when already installed via "npm install -g grunt-cli". Could you mark the nodejs-grunt-cli dependency as optional? Or is there are an alternatvie solution for "check if grunt-cli is already installed, if not install nodejs-grunt-cli from the AUR"?

geekgonecrazy commented on 2014-07-25 23:08

Perfect. Installed with no issues. Thanks!

4javier commented on 2014-07-24 14:05

Try if it works now, please.

4javier commented on 2014-07-24 11:23

At first sight, it seems they changed versioning to 0.41. I'll investigate further soon. (hopefully today)

geekgonecrazy commented on 2014-07-24 01:46

I can install brackets-git but for some reason this package throws:

Switched to a new branch 'makepkg'
-> Creating working copy of brackets git repo...
Cloning into 'brackets'...
done.
fatal: Cannot update paths and switch to branch 'makepkg' at the same time.
Did you intend to checkout 'sprint-41' which can not be resolved as commit?

4javier commented on 2014-07-01 11:24

Added libudev.so.0 as dependency even though I don't like this kind of "hack", because now it's needed for x86 build too.

elpasi commented on 2014-06-30 17:18

Hasn't sprint 41 been out for a while already?

https://github.com/adobe/brackets-shell/commit/f100f39efa9a0f01944e8a8bf0e19ed71f54e85e

https://github.com/adobe/brackets/commit/3da9246ca1a68a1976e17c4e92e6c0b4f6f0b96b#diff-b9cfc7f2cdf78a7f4b91a753d10865a2

elpasi commented on 2014-06-30 17:04

Isn't sprint 41 now out?

4javier commented on 2014-06-27 14:24

@alumni
I know it's outdated, I'm waiting brackets-shell to be updated to sprint-41 too.

4javier commented on 2014-06-27 14:23

I know it's outdated, I'm waiting brackets-shell to be updated to sprint-41 too.

4javier commented on 2014-06-25 21:55

There's no need.
Just keep in mind to read older comments next time.
Cheers.

pedrootavio commented on 2014-06-25 14:10

Thank you, 4javier! It worked after installing the libudev.so.0. Should I delete the post with the error message?

pedrootavio commented on 2014-06-24 23:00

I have installed the libudev.so.0 from AUR and then tried installing brackets again. Unfortunatelly, at the build time an error has occurred:

==> Starting build()...

> Brackets-Shell@0.40.0-0 preinstall /pedro/Libraries/Downloads/brackets/src/brackets-shell
> bash -c 'mv appshell.gyp .appshell.gyp'

npm ERR! cb() never called!
npm ERR! not ok code 0
==> ERROR: A failure occurred in build().
Aborting...

Do you know what might be causing this?

4javier commented on 2014-06-24 20:51

you posted a snippet too short. But if you're on x86_64, it should be solved installing libudev.so.0 from AUR.

pedrootavio commented on 2014-06-24 13:22

The package is returning this error for me:

collect2: error: ld returned 1 exit status
Brackets.target.mk:228: recipe for target 'out/Release/Brackets' failed
make: *** [out/Release/Brackets] Error 1
==> ERROR: A failure occurred in build().
Aborting...

Does anyone know why is it happening?

4javier commented on 2014-05-14 19:46

Yes, I know. I'm trying to figure out why the absence of that file at building-time is a problem for x86_64 and not for x86.

Thanks for your report.

udakak commented on 2014-05-14 18:33

4javier: I needed to install libudev.so.0 to get the package to build.
I'm on x86_64 and did not need lib32-libudev.so.0

4javier commented on 2014-05-12 10:37

there's p7zip as makedepend. Post your building error.

Jengajam3 commented on 2014-05-12 04:28

I would recommend adding unzip to the dependencies, as it is required during build.

4javier commented on 2014-04-29 17:59

Coud you tell me if you need both lib32-libudev.so.0 both libudev.so.0, or if you can compile with just one of them?

digic commented on 2014-04-29 16:26

Yes I am

4javier commented on 2014-04-28 12:36

are you on x86_64 too?

digic commented on 2014-04-28 00:25

I'm getting the same libudev.so.0 errors mentioned previously, and installed the mentioned packages by alexandernst that fixed it.

This being on a fresh install on my desktop, my laptop strangely didn't have this problem after I did a fresh install on it less than a week ago. So not sure what's up with that but thought I'd mention it just in case.

4javier commented on 2014-04-16 00:23

brackets-shell bumped to sprint-38 also.

4javier commented on 2014-04-15 13:16

I'm waiting to see if devs will update brackets-shell to sprint-38 too.

4javier commented on 2014-04-09 12:03

It seems that they restored the site some days ago.
https://github.com/adobe/brackets/issues/7381#issuecomment-39518030

hcjl commented on 2014-04-09 11:16

building now works for me.
thx

hcjl commented on 2014-04-09 11:08

building now work for me.
thx

4javier commented on 2014-04-02 14:13

Yes, I already knew those things. I investigated with a devs on irc to find out the problem. I'll wait a couple days to see if they fix the problem, otherwise we should find a different hosting, and I'll try to patch the grunt task to download from a different mirror. Shouldn't be too difficult.

luka5 commented on 2014-04-02 12:48

I just asked on irc:
[14:21] <@dangoor> luka5: we had some server issues and the server needed to be rebuilt
[14:21] <@dangoor> those files haven't been restored yet
...
[14:25] <@dangoor> yeah, I'm not sure where that stands, but the plan would definitely be to either get that file back up or change where we host it

if you cant wait:
[14:22] <@dangoor> you can get the file here: http://cefbuilds.com/
[14:22] <@dangoor> (but you'll need to uncompress it with 7zip and recompress with zip or change the grunt task because that's what Grunt assumes right now)

luka5 commented on 2014-04-02 11:13

I'm facing the same issue.
In fact the cef zip file is not available.

I already started an issue on github
https://github.com/adobe/brackets/issues/7381

hcjl commented on 2014-04-01 09:08

@4javier
first of all thanks for your effort.
i tried the build in a clean directory with makepkg on serveral machines in serveral networks and i receive the same error on all of them. i also experienced problems with the mirror and i did not manage to download the file manually.

Boushiya commented on 2014-04-01 02:26

I care more about the fact that it's the only un-upgradable package for me, and less about what has actually changed. But hopefully the mirror gets fixed to sort this out. Thanks for keeping this package updated!

4javier commented on 2014-04-01 01:33

There are some problem with dev.brackets.io, that mirrors the CEF download site. Tomorrow I'll try to find a workaround.
This issue affects 32 bit too.

4javier commented on 2014-04-01 01:33

There are some problem with dev.brackets.io, that mirrors the CEF download site. Tomorrow I'll try to find a workaround.

4javier commented on 2014-04-01 00:09

37-2 release differs from the previous one just by the presence of libgcrypt15 in place of libgcrypt inside depends array. Cannot be the culprit. I'll try to investigate.

Boushiya commented on 2014-03-31 21:23

I've been getting the same error as @hcjl over the past few days (as in multiple tries). Please fix it, or revert the package number back to 37-1. (x86_64 environment)

4javier commented on 2014-03-31 18:14

Did you try to clean your building directory and re-execute makepkg? I have no x86_64 environment to test, but nobody else had this issue with the same file. Probably a corruption during download?

hcjl commented on 2014-03-31 13:13

I receive the following error during build.

http://pastebin.com/iasg8JxC

obviously the mentioned zip file is corrupted.

4javier commented on 2014-03-29 12:55

my fault. It depends on libgcrypt15, not libgcrypt.

phyks commented on 2014-03-29 01:58

I have a problem to compile it, it complains about :
/bin/ld: warning: libgcrypt.so.11, needed by Release/libcef.so, not found (try using -rpath or -rpath-link)
Release/libcef.so: référence indéfinie vers « gcry_control@GCRYPT_1.2 »
collect2: erreur: ld a retourné 1 code d'état d'exécution
Brackets.target.mk:224: recipe for target 'out/Release/Brackets' failed
make: *** [out/Release/Brackets] Error 1

Do you have any idea ? Thanks

Full output is here : http://paste.ubuntu.com/7171834/

alexandernst commented on 2014-03-18 14:56

@4javier: You're right, it builds fine once I cleared yaourt's cache. Also the CRLF bug is gone. :)

4javier commented on 2014-03-18 14:34

Please, build in a clean directory through makepkg, not yaourt.

alexandernst commented on 2014-03-18 14:19

@4javier sprint 37 isn't building here: http://paste.ubuntu.com/7114278

4javier commented on 2014-03-18 12:22

Updated.
I have no problem running brackets. Are you sure you didn't modify /opt/brackets/brackets manually?

file /opt/brackets/brackets
/opt/brackets/brackets: Bourne-Again shell script, ASCII text executable

alexandernst commented on 2014-03-18 11:29

Also, brackets in not runnable because of CRLF. Check this:

[alexandernst@stupidbox 0s ~]$ file /opt/brackets/brackets
/opt/brackets/brackets: Bourne-Again shell script, ASCII text executable, with CRLF line terminators
[alexandernst@stupidbox 0s ~]$ brackets
bash: /usr/bin/brackets: /bin/bash^M: bad interpreter: No such file or directory

alexandernst commented on 2014-03-18 07:41

Sprint 37 was just released https://github.com/adobe/brackets/wiki/Release-Notes:-Sprint-37

4javier commented on 2014-03-12 21:25

That should not be required. I fixed the libudev.so.0 issue some times ago. It's strange that only you have this problem.

alexandernst commented on 2014-03-12 12:40

@4javier I'm on x64, anyways, the problem got fixed after I installed:

yaourt -S libudev.so.0 lib32-libudev.so.0


4javier commented on 2014-03-12 12:33

Just tried a totally fresh building, and it's been completed without problems. That warning should be harmful, like it's on my system

/usr/bin/ld: warning: libudev.so.0, needed by Release/libcef.so, not found (try using -rpath or -rpath-link)
LINK(target) out/Release/Brackets: Finished

Are you on 32 or 64 bit?

alexandernst commented on 2014-03-12 09:27

The build is failing:

/usr/bin/ld: warning: libudev.so.0, needed by Release/libcef.so, not found (try using -rpath or -rpath-link)
Release/libcef.so: referencia a `udev_monitor_unref' sin definir
Release/libcef.so: referencia a `udev_enumerate_scan_devices' sin definir
Release/libcef.so: referencia a `udev_new' sin definir
Release/libcef.so: referencia a `udev_list_entry_get_name' sin definir
Release/libcef.so: referencia a `udev_enumerate_get_list_entry' sin definir
Release/libcef.so: referencia a `udev_list_entry_get_next' sin definir
Release/libcef.so: referencia a `udev_device_new_from_syspath' sin definir
Release/libcef.so: referencia a `udev_monitor_receive_device' sin definir
Release/libcef.so: referencia a `udev_device_get_property_value' sin definir
Release/libcef.so: referencia a `udev_unref' sin definir
Release/libcef.so: referencia a `udev_monitor_enable_receiving' sin definir
Release/libcef.so: referencia a `udev_monitor_filter_add_match_subsystem_devtype' sin definir
Release/libcef.so: referencia a `udev_monitor_get_fd' sin definir
Release/libcef.so: referencia a `udev_device_get_devnode' sin definir
Release/libcef.so: referencia a `udev_device_get_subsystem' sin definir
Release/libcef.so: referencia a `udev_enumerate_unref' sin definir
Release/libcef.so: referencia a `udev_enumerate_new' sin definir
Release/libcef.so: referencia a `udev_device_get_parent_with_subsystem_devtype' sin definir
Release/libcef.so: referencia a `udev_monitor_new_from_netlink' sin definir
Release/libcef.so: referencia a `udev_device_unref' sin definir
Release/libcef.so: referencia a `udev_device_get_sysattr_value' sin definir
Release/libcef.so: referencia a `udev_enumerate_add_match_subsystem' sin definir
collect2: error: ld devolvió el estado de salida 1
Brackets.target.mk:224: recipe for target 'out/Release/Brackets' failed
make: *** [out/Release/Brackets] Error 1

4javier commented on 2014-02-08 13:06

Updated. Thanks.

Hindol commented on 2014-02-08 05:29

Sprint 36 is available - http://download.brackets.io/

4javier commented on 2014-01-23 19:08

This new release just add libgcrypt15 as a dependency.

imadalin commented on 2014-01-23 16:07

please add libgcrypt15 as a dependency

4javier commented on 2014-01-16 10:51

I asked the devs if they could make the grunt script for brackets-shell to download a newer version of the CEF, but they said that there are too many bugs with those at this time. Sprint-36 will be released soon, and I will add libgcrypt15 to the depends array.

luka5 commented on 2014-01-16 10:39

@4javier Facing the same issue I installed libgcrypt15 and it worked for me. Thanks

4javier commented on 2014-01-15 18:33

My fault. I didn't investigate further when Xaviju notified me about the problem. I'll look for a way to avoid the hardcoding of the libgcrypt version inside CEF, otherwise i will add libgcrypt15 as a dependency.

Tucker commented on 2014-01-15 14:52

@Xaviju

Installing libgcrypt15 from AUR solves that issue.

4javier commented on 2014-01-14 14:41

It's an error with libgcrypt package, totally unrelated to brackets.
https://bbs.archlinux.org/viewtopic.php?pid=1370456

Xaviju commented on 2014-01-14 08:32

Suddenly today, an error occurred and I was unable to run Brackets or even re-install it after updating Arch:

LINK(target) out/Release/Brackets
/usr/bin/ld: warning: libgcrypt.so.11, needed by Release/libcef.so, not found (try using -rpath or -rpath-link)
Release/libcef.so: undefined reference to `gcry_control@GCRYPT_1.2'
collect2: error: ld returned 1 exit status
Brackets.target.mk:224: recipe for target 'out/Release/Brackets' failed
make: *** [out/Release/Brackets] Error 1
==> ERROR: A failure occurred in build().
Aborting...
==> ERROR: Makepkg was unable to build brackets.

4javier commented on 2014-01-12 12:28

I just tried the Check Update function of brackets, and actually it notifies me of a newer version of brackets available, but if i click on Install Now, it just link to the sprint-35 deb version, that's equivalent to the one i pulled from git. I think it consider (wrongly) the git tag lesser than the deb package. I'll contact the devs as soon as possible.

Commander commented on 2014-01-12 01:59

When I tried to install the git plugin it complained that it needed a newer version.

If you go Help -> check for updates you will notice it will tell about that there is a new build.

"Version 0.8.1 of this extension requires a newer version of Brackets. But you can install the earlier version 0.8.0."

4javier commented on 2014-01-11 12:24

I wrote my last comment a moment after you wrote your one, so I didn't read it. When do brackets notify you of newer version available?

4javier commented on 2014-01-11 11:44

Please don't flag this as out-of-date. At the moment, the only newer tag is v0.36.0-10998, that's an unstable and potentially dangerous release, as wrote inside its description
"But first a BIG WARNING: this is unstable and only lightly tested code. It is unlikely but conceivable that using it could result in data loss or corruption!"

Commander commented on 2014-01-11 11:43

I flagged this but im not sure anymore.

They got the same version name but it seems that they updated the package? Because brackets tells me there is a new version and also plugins complain about it.

4javier commented on 2013-12-27 13:43

p7zip is a makedepend. Are you sure unzip is needed?

BunBum commented on 2013-12-27 07:40

"unzip" dependency should be added because it is needed

4javier commented on 2013-12-20 18:45

The bin one is built against debian libraries, this one is built against Arch libraries. At the moment there shouldn't be any difference. This one download the sources then build them, the other one download pre-compiled binaries.

alexandernst commented on 2013-12-20 16:36

What are the differences between those two?

4javier commented on 2013-12-20 11:49

Because the real git tag is sprint-35 not sprint35, but I can't use the dash inside $pkgver.
Bear in Mind that this is not the old "brackets" pkgbuild that was based on the official .deb build. That one has been kindly renamed to brackets-bin, to leave the name "brackets" to this one, created building sources from scratch.

4javier commented on 2013-12-20 10:37

Because the real git tag is sprint-35 not sprint35, but I can't use the dash inside $pkgver.

alexandernst commented on 2013-12-19 22:57

Why did the name changed from "sprintXX" yo "sprint_XX" ?

4javier commented on 2013-12-06 00:40

libudev.so.0 is a dirtiest hack, I solved the problem in a cleaner way (reccomended by brackets devs) into the brackets.install file. Ignore building error, the program works flawlessy.

kicka commented on 2013-12-05 18:19

Need to add libudev.so.0 to dependancies... otherwise during the compilation make will throw out errors. With libudev.so.0 installed everythings works fine...