Skip to content

Commit

Permalink
Release GE-Proton7-55
Browse files Browse the repository at this point in the history
  • Loading branch information
GloriousEggroll committed Apr 10, 2023
1 parent 6468bc2 commit 7628200
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
GE-Proton7-54
GE-Proton7-55

13 comments on commit 7628200

@weixiaoteleisha
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how to down load

@Endev-R
Copy link

@Endev-R Endev-R commented on 7628200 Apr 22, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how to down load

git1

I used this method:
Open 'terminal' and type this command:
git clone https://github.com/GloriousEggroll/proton-ge-custom.git

I hope this helps

@Endev-R
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hiiiiii, first thanks for developing this software, I installed proton-ge-custom, it's working but I have an issue:
I didn't find 'generate.sh'
@GloriousEggroll how can I find it/add it

I'll be very happy to run my system correctly thanks to your help
git2r

@therealmate
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hiiiiii, first thanks for developing this software, I installed proton-ge-custom, it's working but I have an issue: I didn't find 'generate.sh' @GloriousEggroll how can I find it/add it

I'll be very happy to run my system correctly thanks to your help git2r

https://github.com/GloriousEggroll/proton-ge-custom#manual

@GloriousEggroll
Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Endev-R
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ohh, sorry I didn't do that, thank you @GloriousEggroll and @therealmate

@gabriele2000
Copy link

@gabriele2000 gabriele2000 commented on 7628200 Apr 28, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how to down load

git1

Heh, imagine being someone that asks a basic question and you're speaking in terminal... it's not even the right answer though because you've showed him errors and how to clone from source.

how to down load

  • Open this page https://github.com/GloriousEggroll/proton-ge-custom/releases
  • Download the .tar.gz archive, the one that's almost 400MB
  • Open the archive
  • Now inside the archive there is a folder. You have to put this folder inside another one called "compatibilitytools.d" which is located in your home folder, inside a hidden folder.

So if you want to do it the simple way:

  • Open the file manager and enable "show hidden files"
  • Navigate into .steam
  • Navigate into debian-installation and compatibilitytools.d
  • Put the folder there like this
    image

@GloriousEggroll Almost 400MB is a lot BTW, it's easily compressible using ZSTD which everything can open it (everything built in any distro nowadays).
Is there a chance that it'll happen?

ZSTD preset 10 - 334MB
ZSTD preset 8 - 348MB
ZSTD preset 6 - 354MB
ZSTD preset 22 (if you're crazy) - 206MB

@Endev-R
Copy link

@Endev-R Endev-R commented on 7628200 Apr 28, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Woooooooow, thank you very much, that day was my second day with Linux (and I thought that I did it correctly but I DIDN'T)
I'll try doing it this way (I even thought that when I clone something it will be automatically installed hhh, anyway thank you very very much for this detailed explanation)
@gabriele2000

This method is a lot better than the crap I thought would work (two days trying to figure out how to do it then I gave up on it until you sent me this)

@gabriele2000
Copy link

@gabriele2000 gabriele2000 commented on 7628200 Apr 28, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Woooooooow, thank you very much, that day was my second day with Linux (and I thought that I did it correctly but I DIDN'T) I'll try doing it this way (I even thought that when I clone something it will be automatically installed hhh, anyway thank you very very much for this detailed explanation) @gabriele2000

This method is a lot better than the crap I thought would work (two days trying to figure out how to do it then I gave up on it until you sent me this)

Glad I could help, btw sorry if I had the "wrong tone", I see a lot of people that just say "just compile it" and stuff like that; a beginner wouldn't understand this because you have to start from the basics.

Anyway, compiling is harder, sometimes by a few "points", sometimes it takes an entire week just to figure out that you can't build it because maybe you're using an outdated package, maybe you can only compile it on Arch or maybe you need an older version and yours is too new.

You also can use a tool like ProtonUp - Qt.

There are two versions:

  • Flatpak
  • Appimage

Most likely you can't run .Appimage files in a easy way YET, but let's pick the easiest way since most distros have Flatpak preinstalled.
Appimages are like android apps: you have a single file which contains everything that's needed; Flatpaks are similar, but are engineered in a different way.
Both are sandboxed (isolated from the main system, think of it like an entire drive which only a program inside it and that program doesn't know anything else) but Flatpaks are more integrated with the system.

To install the flatpak version, you can open the terminal (recommended since it's a simple line) and write
flatpak install protonupqt
Flatpak is the package manager, you're installing "protonupqt".

You can also write flatpak install net.davidotek.pupgui2 and that would be even better.

Why?
Because is flatpak searches for protonupqt and finds protonupqt2 it'll asks which one do you want to install, which is no problem, but if you're (for example) unsure and you type the correct name, you're the safest you can get.

Important: flatpak will ask you if you want to install it as system or user.
Always pick user unless you have more profiles (as in Users that uses that computer) and you want that specific package (and its dependencies) installed system wide (so, for example, your friend wants to install Proton-GE 7.55 easily (unlikely, Proton-GE 8 will likely come out very soon).

An interesting thing: notice how flatpaks IDs are like android apps... something like com.google.playstore or com.sony.music

EDIT: I forgot that I wanted to explain one more thing.

I even thought that when I clone something it will be automatically installed

This is tricky.
There are, like, 2 out of 1000 programs that are "ready to use" right after cloning... most likely Python scripts.
Cloning something implies that you have something that you too want, exactly as it is, on your computer (so, offline).

Cloning is the main step for compiling stuff, usually.
Compiling WINE is harder that most of other things, trust me.
Stuff like 32-bit and 64-bit dependencies, in a Distro where the core is still stuck on Ubuntu 22.04 (and even Ubuntu 23.04 has outdated or missing packages) and... Ubuntu-based Distros are THE WORST for compiling WINE, because of "dependency-hell".

It'll come a day when something will breaks inside APT (the main package manager of Debian/Ubuntu-based Distros) and you'll encounter an angry-inducing situation:

  • You can't install package A because package B is too old
  • You can't install package B because package C can't be installed (B requests C 1.2 but your Distro version only has 1.1 available)

WINE 8 has the option to run 32-bit stuff inside a 64-bit only prefix, but that's still experimental (you totally can get rid of almost every 32-bit package, except graphics drivers).

@Endev-R
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you very much for the information!!!!! That's super nice from you and I'm sure it will help me a lot, OMG this is great, thank YOUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU @gabriele2000

@gabriele2000
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you very much for the information!!!!! That's super nice from you and I'm sure it will help me a lot, OMG this is great, thank YOUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU @gabriele2000

Ahaha glad I could help!

@loathingKernel
Copy link

@loathingKernel loathingKernel commented on 7628200 May 1, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Individual commit comments are not a general Issues tracker nor a help forum. Issues in this repository are disabled for a reason. Discussions and questions happen on discord. Stop polluting this comment section with spammy comments.

@Gabriele200 If you consider these instructions to be of value , a better way to make them visible and retain them is to format them to fit the README and make a PR to add them. They will eventually be lost here.

@gabriele2000
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Individual commit comments are not a general Issues tracker nor a help forum. Issues in this repository are disabled for a reason. Discussions and questions happen on discord. Stop polluting this comment section with spammy comments.

I deeply apologize, I was trying to help a user and I didn't think much of it.

@Gabriele200 If you consider these instructions to be of value , a better way to make them visible and retain them is to format them to fit the README make a PR to add them. They will eventually be lost here.

Heh, you gave me a cool idea, you know?
By the way, I don't think I've said something more than what's on the README, but I'll inspect it and make changes if I see fit.

Please sign in to comment.