Brackets is an open source code editor for the web. It's built with JavaScript, HTML and CSS by web developers like you. Reproducible: Always
37 is out.
Version 0.44 is out.
Created attachment 386324 [details] ebuild of brackets-0.44 Hi, I've actually wrote some early, ugly but seems-to working ebuild of recent Brackets editor. Please send errors and/or suggestions of their fixes.
(In reply to deim from comment #3) > Created attachment 386324 [details] > ebuild of brackets-0.44 > > Hi, I've actually wrote some early, ugly but seems-to working ebuild of > recent Brackets editor. Please send errors and/or suggestions of their fixes. Can you modify your ebuild to build from source? Btw: Adobe released version 1.0 [1]. [1] http://blog.brackets.io/2014/11/04/brackets-1-0-and-extract-for-brackets-preview-now-available/
Created attachment 388826 [details] ebuild of brackets-bin-0.44 and 1.0 Install still from .deb packages, need more time or help to prepare install from source :-/ Maybe will help analysis of install package from Arch.
(moved .deb installation from brackets to brackets-bin)
Brackets uses the Chromium Embedded Framework (CEF), therefore this bug should depend on bug #529604
Thanks for the ebuilds! What is the intended purpose of the chromium use flag? Also, the brackets binaries need libgcrypt.so.11 and do not work if only dev-libs/libgcrypt-1.6.x is installed. Therefore the ebuild should depend on dev-libs/libgcrypt:11 or similar. Regards, Fabian
(In reply to Fabian Köster from comment #8) > What is the intended purpose of the chromium use flag? Brackets have live-view function and uses chrome. I don't use this feature, so it may not be fully correctly defined in ebuild. > Also, the brackets binaries need libgcrypt.so.11 and do not work if only > dev-libs/libgcrypt-1.6.x is installed. Therefore the ebuild should depend on > > dev-libs/libgcrypt:11 > > or similar. It's possible, modify ebuild as you like and you could paste the corrected one here :)
Brackets 1.1 is out.
Created attachment 395230 [details] brackets-bin/brackets-bin-1.1.ebuild
After upgrade to 1.1 It says unknown error when installing or upgrading plugins. Don't someone know how to fix it?
Works fine here.
1.2 is out. I found this: https://github.com/ub1quit33/GentooOverlays/tree/master/app-editors/brackets Didn't try yet, what do you think?
(In reply to deim from comment #14) > 1.2 is out. > > I found this: > https://github.com/ub1quit33/GentooOverlays/tree/master/app-editors/brackets > Didn't try yet, what do you think? Very interesting! Seems like the CEF sources are included in the downloaded tarball and it is build from source. I will try it as soon as I have some time for it.
(In reply to deim from comment #14) > 1.2 is out. > > I found this: > https://github.com/ub1quit33/GentooOverlays/tree/master/app-editors/brackets > Didn't try yet, what do you think? I just tried it, it builds brackets from source but downloads CEF as a binary, so its not a full source build. Also, the versioned ebuild (0.34.0) is quite outdated.
Created attachment 400750 [details] brackets-bin-1.2.ebuild Binary ebuild for Brackets 1.2
Created attachment 402328 [details] brackets-1.3.ebuild
Created attachment 402330 [details, diff] bracketsshell_appshell.gyp.patch
Created attachment 402332 [details, diff] bracketsshell_appshell_extensions_gtk.cpp.patch
Created attachment 402334 [details, diff] bracketsshell_appshell_extensions_platform.h.patch
Created attachment 402336 [details, diff] bracketsshell_appshell_node_process_linux.cpp.patch
Created attachment 402338 [details, diff] bracketsshell_appshell_paths.gypi.patch
Created attachment 402340 [details, diff] bracketsshell_cefclient.cpp.patch
Created attachment 402342 [details, diff] bracketsshell_cefclient.h.patch
Created attachment 402344 [details, diff] bracketsshell_cefclient_gtk.cpp.patch
Created attachment 402346 [details, diff] bracketsshell_client_app_gtk.cpp.patch
Created attachment 402348 [details, diff] bracketsshell_client_handler.cpp.patch
Created attachment 402350 [details, diff] bracketsshell_client_handler.h.patch
Created attachment 402352 [details, diff] bracketsshell_client_handler_gtk.cpp.patch
Created attachment 402354 [details, diff] bracketsshell_gitignore.patch
Created attachment 402356 [details, diff] bracketsshell_Gruntfile.js.patch
Created attachment 402358 [details, diff] bracketsshell_resource_util_linux.cpp.patch
Here we go. I added an ebuild for brackets to build it by source. It fetches the file from git this time because there is a problem with the current 1.3 release files (https://github.com/adobe/brackets/issues/10656). Also it includes the CEF2171-fix to be buildable under linux (https://github.com/adobe/brackets-shell/pull/499) @Fabian Köster: CEF is always included as binary by brackets, it's downloaded via npm and it's the recommended building procedure for it.
(In reply to Nicolas Pöhlmann from comment #34) > Here we go. I added an ebuild for brackets to build it by source. It fetches > the file from git this time because there is a problem with the current 1.3 > release files (https://github.com/adobe/brackets/issues/10656). > > Also it includes the CEF2171-fix to be buildable under linux > (https://github.com/adobe/brackets-shell/pull/499) Wow, thanks for all the work! I will try it out later. > @Fabian Köster: > CEF is always included as binary by brackets, it's downloaded via npm and > it's the recommended building procedure for it. This might be true but nevertheless it is not compliant with the Gentoo policies for source ebuilds, check for example [1]. Also the download via npm thwarts any mirror or caching system for distfiles. [1] https://wiki.gentoo.org/wiki/Why_not_bundle_dependencies
You are right about the policy complaints, but this is not (only) a problem with this ebuild. If the user had build Cef from source and installed it globally before building brackets via this ebuild, there should be no binary building at all. The binary building process is a problem with npm packages, to be 100% Gentoo conform when building packages via npm/grunt every package which also has a binary counterpart need an extra ebuild to be sure that it is build via source and installed globally. Building the complete Chromium Embedded Framework (Cef) from source inside the brackets ebuild would be an overkill like building gcc inside each ebuild. The right way to fix the building from source is creating another ebuild for Cef which brackets should then depend on or just a simple check in the ebuild with instructions how to build and install cef via npm before the ebuild could be run.
(In reply to Nicolas Pöhlmann from comment #36) > You are right about the policy complaints, but this is not (only) a problem > with this ebuild. > > If the user had build Cef from source and installed it globally before > building brackets via this ebuild, there should be no binary building at all. > > The binary building process is a problem with npm packages, to be 100% > Gentoo conform when building packages via npm/grunt every package which also > has a binary counterpart need an extra ebuild to be sure that it is build > via source and installed globally. > > Building the complete Chromium Embedded Framework (Cef) from source inside > the brackets ebuild would be an overkill like building gcc inside each > ebuild. > The right way to fix the building from source is creating another ebuild for > Cef which brackets should then depend on or just a simple check in the > ebuild with instructions how to build and install cef via npm before the > ebuild could be run. Thats why I added the bug #529604 and created a dependency on it from this bug. Every npm dependency should be replaced by an corresponding ebuild dependency. I never said anything else. Of course it is a lot of work.
Nice work, thank you! But I have problems while editing file in compiled brackets. I can modify document by keyboard but when I click to document - keyboard modification si disabled so I must click to another window and then back to enable keyboard modifications. Don't know why - here's console output: $ brackets [0522/094306:ERROR:browser_main_loop.cc(163)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki/LinuxSUIDSandboxDevelopment for more information on developing with the sandbox on. ATTENTION: default value of option force_s3tc_enable overridden by environment. [0522/094306:ERROR:sandbox_linux.cc(305)] InitializeSandbox() called with multiple threads in process gpu-process [0522/094306:ERROR:gpu_process_transport_factory.cc(437)] Failed to establish GPU channel. [0522/094307:ERROR:renderer_main.cc(207)] Running without renderer sandbox
Could someone make a 1.4 ebuild please? https://github.com/adobe/brackets/wiki/Release-Notes:-1.4
Hello 1.6 has been out for a while: https://github.com/adobe/brackets/wiki/Release-Notes:-1.6
Quickly - if someone want's to install latest brackets-bin it's easy - just download latest here uploaded ebuild, rename it's version and make manifest as usual. Currently I don't use compiled version since it doesn't run well on my PC.
deim including all patches? Do they still apply to 1.6?
Created attachment 436222 [details] brackets-bin-1.6 ebuild this is my actual brackets-bin ebuild
Works great deim, thanks!
Created attachment 442870 [details] brackets-bin-1.7.ebuild Installs and runs fine.
Need to include paxctl -c and paxctl -m commands in the ebuilds so that it runs on Hardened Gentoo. Not sure how it is done in other ebuilds on top of my head. Also, is it possible to build it from source? BTW, https://github.com/zaggino/brackets-electron does a much better job on my Hardened Gentoo HiDPI laptop.
Created attachment 445636 [details] app-editors/brackets-bin-1.7 ebuild with pax marking Attaching ebuild with pax marking for hardened kernels.
Created attachment 445638 [details] brackets-electron-bin-1.8.2.ebuild Attaching ebuild for app-editors/brackets-electron-bin-1.8.2 brackets-electron is a fork from brackets and is currently at 1.8 which has support for HiDPI which is broken in brackets and will be fixed by 1.8 release.
Brackets 1.9 has been out for a month.
Please add Brackets-1.11
beware of menu font error in 1.11 (1.10 is OK) https://github.com/adobe/brackets/issues/13738
Could someone post an ebuild for brackets 1.12?
Created attachment 518886 [details] ebuild of brackets 1.12 here You are :-)
What fantastic service, thank you ;] Emerged 1.12 (in Sabayon), seems to be working fine.
What's the reason this is not in portage yet?
(In reply to DrSlony from comment #55) > What's the reason this is not in portage yet? Well to me it looks like no one is willing to / doesnt know how to maintain it in portage. There's a nice way to do this with proxy-maintainer project, https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers Its a lot of information to take in, but if you study it a bit, you can get this package to Gentoo's main portage. Currently it looks like the proxy-maint team is a bit overworked, but the faster you start, the faster it gets in the tree ;) and looking at this bug, there seems to be interest in maintaining this package.
Brackets 1.13 is out.
I renamed the ebuild to 1.13 and it installted and seems to run fine.
Not worked in Brackets for a while now I tried to run it (v1.14) and it didn't start so I tried this: https://data.gpo.zugaina.org/linxon/app-editors/brackets-bin/brackets-bin-1.14.ebuild and modify to newest v1.14.1 but it didn't help - tried to remove redirection to /dev/null in run script and output gives me: [0911/194045:FATAL:udev_loader.cc(38)] Check failed: false. SIGABRT
