Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CLOSED] Update README.md to remove 'debian/ubuntu' #10255 #10963

Open
core-ai-bot opened this issue Aug 30, 2021 · 6 comments
Open

[CLOSED] Update README.md to remove 'debian/ubuntu' #10255 #10963

core-ai-bot opened this issue Aug 30, 2021 · 6 comments

Comments

@core-ai-bot
Copy link
Member

Issue by jacebenson
Sunday Nov 06, 2016 at 23:28 GMT
Originally opened as adobe/brackets#12876


Changing Linux(Debian/Ubuntu) to just Linux as Debian based Linux flavors no longer install and won't continue based on comments by ficristo here adobe/brackets#10255 (comment)

Ultimately this has a work around but I don't see how to edit the wiki pages on adobe/brackets. I'll be opening an issue with that as the ask which is to change the wiki pages to make it clear you can install on Debian.

I'm unsure what version of CEF is used for brackets here, but it does appear maintained if it's this one;
https://bitbucket.org/chromiumembedded/cef/

With that being said, they have a similar issue and have it as "WONTFIX"
https://bitbucket.org/chromiumembedded/cef/issues?q=libgcrypt

So pretty much unless someone finds and fixes there issue for them either the .deb will no longer work on debian os's that dont come packed with libgcrypt11 so all of them.


jacebenson included the following code: https://github.com/adobe/brackets/pull/12876/commits

@core-ai-bot
Copy link
Member Author

Comment by petetnt
Monday Nov 07, 2016 at 09:25 GMT


Hi@jacebenson,

could you sign our CLA? See http://dev.brackets.io/brackets-contributor-license-agreement.html

@core-ai-bot
Copy link
Member Author

Comment by jacebenson
Monday Nov 07, 2016 at 12:30 GMT


Signed just now.

On Nov 7, 2016, at 3:26 AM, Pete Nykänen notifications@github.com wrote:

Hi@jacebenson,

could you sign our CLA? See http://dev.brackets.io/brackets-contributor-license-agreement.html


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@core-ai-bot
Copy link
Member Author

Comment by ficristo
Monday Nov 07, 2016 at 19:09 GMT


Signed just now.

Thank you.

But personally I'm for WONTFIXing this.
I think the "Debian/Ubuntu" is a way to say that we produce only .deb packages so other platforms are not supported. If you remove it, it will seems that we support more platforms which is not correct.

Linux builds are build from the linux-1547 branch which use the 1547 version of CEF.
To fix the libgcrypto we have to update CEF version and probably merge this one adobe/brackets-shell#501

PS: I have some PR on brackets-shell, which are already available in the repo, to build with a newer version of CEF, but we need support from Adobe to reach a conclusion. And sincerly with brackets-electron available I would like to simply switch to it: adobe/brackets#12857.

@core-ai-bot
Copy link
Member Author

Comment by jacebenson
Friday Nov 18, 2016 at 05:07 GMT


@ficristo changing to electron would be cool but I was under the impression that wasn't going to happen per your comment before #10255 was locked. If it did that'd be awesome. I've been playing with atom as I jump around from windows to linux and like the same editor. I'll keep watching for this change but I am not holding my breath.

@core-ai-bot
Copy link
Member Author

Comment by petetnt
Friday Nov 18, 2016 at 08:06 GMT


@jacebenson have you checked out zaggino/brackets-electron? It has (near) feature parity with the CEF version and it's maintained by one of our contributors. I think that switching at this point wouldn't be so farfetched.

@core-ai-bot
Copy link
Member Author

Comment by ficristo
Wednesday Nov 23, 2016 at 18:49 GMT


I don't know if we will switch to electron officially (I'm totally in favor for it), but the fork of@zaggino is very well alive. And, especially if you are a Linux user, I strongly advice to switch to it.

Regarding this PR, I think it will make things a bit more confusing, so I close it for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant