build(linux): drop support for AUR

[ReenigneArcher]

Description

Dropping support for ArchLinux AUR as I am not willing to constantly battle people like @xiota, @dr460nf1r3. No bug reports will be accepted from users using any AUR package.

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 8.99%. Comparing base (5cea1e1) to head (cd097e3).
Report is 136 commits behind head on master.

Additional details and impacted files

@@ Coverage Diff @@## master #2819 +/- ##
======================================
Coverage 8.98% 8.99% ======================================
Files 95 95 Lines 17304 17310 +6 Branches 8232 8234 +2 ======================================
+ Hits 1555 1557 +2 - Misses 12884 12888 +4 
Partials 2865 2865 

Flag	Coverage Δ
Linux	6.80% <ø> (+0.01%)	⬆️
Windows	4.16% <ø> (-0.01%)	⬇️
macOS-12	10.10% <ø> (+<0.01%)	⬆️
macOS-13	10.02% <ø> (+<0.01%)	⬆️
macOS-14	10.31% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[hilts-vaughan]

Has LizardByte considered setting up their own repository? It would allow more control and less harassment. However, I understand it is easier to simply not support it.

Thanks for at least providing a manual install option. I personally will be removing the AUR package as I can't in good faith trust someone who is willing to usurp a package like that when the upstream maintainer was doing it for so long.

Thanks for everything!

[ReenigneArcher]

@hilts-vaughan I was looking into that, although the repo would just be the 2-3 files that are in the new sunshine.pkg.tar.gz release asset.

I guess the advantage would be for the user when it comes to updates, so I will try to come up a with a way to do this, and keep things hosted on GitHub. I do see AUR has a mirror on GitHub, for which it would be super easy to setup an equivalent... but how can a user point to such a repo hosted in GitHub?

There doesn't seem to be much info on the web about hosting a private AUR. Maybe these two tools can help (I need to investigate it a little more).

• https://github.com/pacman-repo-builder/pacman-repo-builder
• https://github.com/pacman-repo-builder/action

[hilts-vaughan]

I wish I had more information to offer, sorry. I just consumed a few for a while (AUR helpers used to use them, archlinux.fr had one for some time) Given there is tooling, obviously some people maintain them as well.. but setting up an entire package repo for a few files seems like a lot of work an infrastructure for you to have to maintain. :(

It's pretty trivial for users to point their CLI tool at a PKGBUILD though -- so even that would be helpful (though again, easy to point it at the artfact too) but without the other repo bits you don't get auto update.

[ReenigneArcher]

It looks like it actually won't be all that difficult. Here's an example. https://github.com/KSXGitHub/pacman-repo

I will play with it more in the coming days.

[ReenigneArcher]

@hilts-vaughan I have created a self hosted pacman repo, here: https://github.com/LizardByte/pacman-repo

It contains PKGBUILDs and rebuilds packages once a day, so users shouldn't even necessarily need the PKGBUILD anymore.

[patod01]

@ReenigneArcher Hi! I've been looking forward the next release since I saw the new feature of naming and deleting clients one by one. I'm a new linux user running away from windows and I chose arch like 5 months ago.

Today I was in this repository again to read the pre-releases notes once again and I just found a "read more" link, then I found out the AUR drama and it made me stare at the horizon for a while after reading all the messages there.

I don't know if this is the best place to write to you, but I just wanted to say thanks for your work. It makes me a bit sad the results of the discussion, but if you're better now, that's great. And, being positive, you motivated me to make my own repo once I learn to program well enough and have some projects! Because, certainly I enjoy pacman way more than apt, so if I change distro in the future, I'll keep using it.

I will be switching to your pacman repo next sunday. Waiting for the next stable release of this project has been like waiting for xmas for me. I can't stop reading the changelog every week. Thanks again and have a nice weekend!

[ReenigneArcher]

Thank you. The next stable release will "probably" be coming soon-ish. With that said, beta/pre-releases are usually pretty solid. Beta is also available in https://github.com/LizardByte/pacman-repo

[ReenigneArcher]

Description

Dropping support for ArchLinux AUR as I am not willing to constantly battle people like @xiota, @dr460nf1r3. No bug reports will be accepted from users using any AUR package.

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 8.99%. Comparing base (5cea1e1) to head (cd097e3).
Report is 136 commits behind head on master.

Additional details and impacted files

@@ Coverage Diff @@## master #2819 +/- ##
======================================
Coverage 8.98% 8.99% ======================================
Files 95 95 Lines 17304 17310 +6 Branches 8232 8234 +2 ======================================
+ Hits 1555 1557 +2 - Misses 12884 12888 +4 
Partials 2865 2865 

Flag	Coverage Δ
Linux	6.80% <ø> (+0.01%)	⬆️
Windows	4.16% <ø> (-0.01%)	⬇️
macOS-12	10.10% <ø> (+<0.01%)	⬆️
macOS-13	10.02% <ø> (+<0.01%)	⬆️
macOS-14	10.31% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[hilts-vaughan]

Has LizardByte considered setting up their own repository? It would allow more control and less harassment. However, I understand it is easier to simply not support it.

Thanks for at least providing a manual install option. I personally will be removing the AUR package as I can't in good faith trust someone who is willing to usurp a package like that when the upstream maintainer was doing it for so long.

Thanks for everything!

[ReenigneArcher]

@hilts-vaughan I was looking into that, although the repo would just be the 2-3 files that are in the new sunshine.pkg.tar.gz release asset.

I guess the advantage would be for the user when it comes to updates, so I will try to come up a with a way to do this, and keep things hosted on GitHub. I do see AUR has a mirror on GitHub, for which it would be super easy to setup an equivalent... but how can a user point to such a repo hosted in GitHub?

There doesn't seem to be much info on the web about hosting a private AUR. Maybe these two tools can help (I need to investigate it a little more).

• https://github.com/pacman-repo-builder/pacman-repo-builder
• https://github.com/pacman-repo-builder/action

[hilts-vaughan]

I wish I had more information to offer, sorry. I just consumed a few for a while (AUR helpers used to use them, archlinux.fr had one for some time) Given there is tooling, obviously some people maintain them as well.. but setting up an entire package repo for a few files seems like a lot of work an infrastructure for you to have to maintain. :(

It's pretty trivial for users to point their CLI tool at a PKGBUILD though -- so even that would be helpful (though again, easy to point it at the artfact too) but without the other repo bits you don't get auto update.

[ReenigneArcher]

It looks like it actually won't be all that difficult. Here's an example. https://github.com/KSXGitHub/pacman-repo

I will play with it more in the coming days.

[ReenigneArcher]

@hilts-vaughan I have created a self hosted pacman repo, here: https://github.com/LizardByte/pacman-repo

It contains PKGBUILDs and rebuilds packages once a day, so users shouldn't even necessarily need the PKGBUILD anymore.

[patod01]

@ReenigneArcher Hi! I've been looking forward the next release since I saw the new feature of naming and deleting clients one by one. I'm a new linux user running away from windows and I chose arch like 5 months ago.

Today I was in this repository again to read the pre-releases notes once again and I just found a "read more" link, then I found out the AUR drama and it made me stare at the horizon for a while after reading all the messages there.

I don't know if this is the best place to write to you, but I just wanted to say thanks for your work. It makes me a bit sad the results of the discussion, but if you're better now, that's great. And, being positive, you motivated me to make my own repo once I learn to program well enough and have some projects! Because, certainly I enjoy pacman way more than apt, so if I change distro in the future, I'll keep using it.

I will be switching to your pacman repo next sunday. Waiting for the next stable release of this project has been like waiting for xmas for me. I can't stop reading the changelog every week. Thanks again and have a nice weekend!

[ReenigneArcher]

Thank you. The next stable release will "probably" be coming soon-ish. With that said, beta/pre-releases are usually pretty solid. Beta is also available in https://github.com/LizardByte/pacman-repo

[ReenigneArcher]

Description

Dropping support for ArchLinux AUR as I am not willing to constantly battle people like @xiota, @dr460nf1r3. No bug reports will be accepted from users using any AUR package.

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 8.99%. Comparing base (5cea1e1) to head (cd097e3).
Report is 136 commits behind head on master.

Additional details and impacted files

@@ Coverage Diff @@## master #2819 +/- ##
======================================
Coverage 8.98% 8.99% ======================================
Files 95 95 Lines 17304 17310 +6 Branches 8232 8234 +2 ======================================
+ Hits 1555 1557 +2 - Misses 12884 12888 +4 
Partials 2865 2865 

Flag	Coverage Δ
Linux	6.80% <ø> (+0.01%)	⬆️
Windows	4.16% <ø> (-0.01%)	⬇️
macOS-12	10.10% <ø> (+<0.01%)	⬆️
macOS-13	10.02% <ø> (+<0.01%)	⬆️
macOS-14	10.31% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[hilts-vaughan]

Has LizardByte considered setting up their own repository? It would allow more control and less harassment. However, I understand it is easier to simply not support it.

Thanks for at least providing a manual install option. I personally will be removing the AUR package as I can't in good faith trust someone who is willing to usurp a package like that when the upstream maintainer was doing it for so long.

Thanks for everything!

[ReenigneArcher]

@hilts-vaughan I was looking into that, although the repo would just be the 2-3 files that are in the new sunshine.pkg.tar.gz release asset.

I guess the advantage would be for the user when it comes to updates, so I will try to come up a with a way to do this, and keep things hosted on GitHub. I do see AUR has a mirror on GitHub, for which it would be super easy to setup an equivalent... but how can a user point to such a repo hosted in GitHub?

There doesn't seem to be much info on the web about hosting a private AUR. Maybe these two tools can help (I need to investigate it a little more).

• https://github.com/pacman-repo-builder/pacman-repo-builder
• https://github.com/pacman-repo-builder/action

[hilts-vaughan]

I wish I had more information to offer, sorry. I just consumed a few for a while (AUR helpers used to use them, archlinux.fr had one for some time) Given there is tooling, obviously some people maintain them as well.. but setting up an entire package repo for a few files seems like a lot of work an infrastructure for you to have to maintain. :(

It's pretty trivial for users to point their CLI tool at a PKGBUILD though -- so even that would be helpful (though again, easy to point it at the artfact too) but without the other repo bits you don't get auto update.

[ReenigneArcher]

It looks like it actually won't be all that difficult. Here's an example. https://github.com/KSXGitHub/pacman-repo

I will play with it more in the coming days.

[ReenigneArcher]

@hilts-vaughan I have created a self hosted pacman repo, here: https://github.com/LizardByte/pacman-repo

It contains PKGBUILDs and rebuilds packages once a day, so users shouldn't even necessarily need the PKGBUILD anymore.

[patod01]

@ReenigneArcher Hi! I've been looking forward the next release since I saw the new feature of naming and deleting clients one by one. I'm a new linux user running away from windows and I chose arch like 5 months ago.

Today I was in this repository again to read the pre-releases notes once again and I just found a "read more" link, then I found out the AUR drama and it made me stare at the horizon for a while after reading all the messages there.

I don't know if this is the best place to write to you, but I just wanted to say thanks for your work. It makes me a bit sad the results of the discussion, but if you're better now, that's great. And, being positive, you motivated me to make my own repo once I learn to program well enough and have some projects! Because, certainly I enjoy pacman way more than apt, so if I change distro in the future, I'll keep using it.

I will be switching to your pacman repo next sunday. Waiting for the next stable release of this project has been like waiting for xmas for me. I can't stop reading the changelog every week. Thanks again and have a nice weekend!

[ReenigneArcher]

Thank you. The next stable release will "probably" be coming soon-ish. With that said, beta/pre-releases are usually pretty solid. Beta is also available in https://github.com/LizardByte/pacman-repo

[ReenigneArcher]

Description

Dropping support for ArchLinux AUR as I am not willing to constantly battle people like @xiota, @dr460nf1r3. No bug reports will be accepted from users using any AUR package.

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 8.99%. Comparing base (5cea1e1) to head (cd097e3).
Report is 136 commits behind head on master.

Additional details and impacted files

@@ Coverage Diff @@## master #2819 +/- ##
======================================
Coverage 8.98% 8.99% ======================================
Files 95 95 Lines 17304 17310 +6 Branches 8232 8234 +2 ======================================
+ Hits 1555 1557 +2 - Misses 12884 12888 +4 
Partials 2865 2865 

Flag	Coverage Δ
Linux	6.80% <ø> (+0.01%)	⬆️
Windows	4.16% <ø> (-0.01%)	⬇️
macOS-12	10.10% <ø> (+<0.01%)	⬆️
macOS-13	10.02% <ø> (+<0.01%)	⬆️
macOS-14	10.31% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[hilts-vaughan]

Has LizardByte considered setting up their own repository? It would allow more control and less harassment. However, I understand it is easier to simply not support it.

Thanks for at least providing a manual install option. I personally will be removing the AUR package as I can't in good faith trust someone who is willing to usurp a package like that when the upstream maintainer was doing it for so long.

Thanks for everything!

[ReenigneArcher]

@hilts-vaughan I was looking into that, although the repo would just be the 2-3 files that are in the new sunshine.pkg.tar.gz release asset.

I guess the advantage would be for the user when it comes to updates, so I will try to come up a with a way to do this, and keep things hosted on GitHub. I do see AUR has a mirror on GitHub, for which it would be super easy to setup an equivalent... but how can a user point to such a repo hosted in GitHub?

There doesn't seem to be much info on the web about hosting a private AUR. Maybe these two tools can help (I need to investigate it a little more).

• https://github.com/pacman-repo-builder/pacman-repo-builder
• https://github.com/pacman-repo-builder/action

[hilts-vaughan]

I wish I had more information to offer, sorry. I just consumed a few for a while (AUR helpers used to use them, archlinux.fr had one for some time) Given there is tooling, obviously some people maintain them as well.. but setting up an entire package repo for a few files seems like a lot of work an infrastructure for you to have to maintain. :(

It's pretty trivial for users to point their CLI tool at a PKGBUILD though -- so even that would be helpful (though again, easy to point it at the artfact too) but without the other repo bits you don't get auto update.

[ReenigneArcher]

It looks like it actually won't be all that difficult. Here's an example. https://github.com/KSXGitHub/pacman-repo

I will play with it more in the coming days.

[ReenigneArcher]

@hilts-vaughan I have created a self hosted pacman repo, here: https://github.com/LizardByte/pacman-repo

It contains PKGBUILDs and rebuilds packages once a day, so users shouldn't even necessarily need the PKGBUILD anymore.

[patod01]

@ReenigneArcher Hi! I've been looking forward the next release since I saw the new feature of naming and deleting clients one by one. I'm a new linux user running away from windows and I chose arch like 5 months ago.

Today I was in this repository again to read the pre-releases notes once again and I just found a "read more" link, then I found out the AUR drama and it made me stare at the horizon for a while after reading all the messages there.

I don't know if this is the best place to write to you, but I just wanted to say thanks for your work. It makes me a bit sad the results of the discussion, but if you're better now, that's great. And, being positive, you motivated me to make my own repo once I learn to program well enough and have some projects! Because, certainly I enjoy pacman way more than apt, so if I change distro in the future, I'll keep using it.

I will be switching to your pacman repo next sunday. Waiting for the next stable release of this project has been like waiting for xmas for me. I can't stop reading the changelog every week. Thanks again and have a nice weekend!

[ReenigneArcher]

Thank you. The next stable release will "probably" be coming soon-ish. With that said, beta/pre-releases are usually pretty solid. Beta is also available in https://github.com/LizardByte/pacman-repo

[ReenigneArcher]

Description

Dropping support for ArchLinux AUR as I am not willing to constantly battle people like @xiota, @dr460nf1r3. No bug reports will be accepted from users using any AUR package.

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 8.99%. Comparing base (5cea1e1) to head (cd097e3).
Report is 136 commits behind head on master.

Additional details and impacted files

@@ Coverage Diff @@## master #2819 +/- ##
======================================
Coverage 8.98% 8.99% ======================================
Files 95 95 Lines 17304 17310 +6 Branches 8232 8234 +2 ======================================
+ Hits 1555 1557 +2 - Misses 12884 12888 +4 
Partials 2865 2865 

Flag	Coverage Δ
Linux	6.80% <ø> (+0.01%)	⬆️
Windows	4.16% <ø> (-0.01%)	⬇️
macOS-12	10.10% <ø> (+<0.01%)	⬆️
macOS-13	10.02% <ø> (+<0.01%)	⬆️
macOS-14	10.31% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[hilts-vaughan]

Has LizardByte considered setting up their own repository? It would allow more control and less harassment. However, I understand it is easier to simply not support it.

Thanks for at least providing a manual install option. I personally will be removing the AUR package as I can't in good faith trust someone who is willing to usurp a package like that when the upstream maintainer was doing it for so long.

Thanks for everything!

[ReenigneArcher]

@hilts-vaughan I was looking into that, although the repo would just be the 2-3 files that are in the new sunshine.pkg.tar.gz release asset.

I guess the advantage would be for the user when it comes to updates, so I will try to come up a with a way to do this, and keep things hosted on GitHub. I do see AUR has a mirror on GitHub, for which it would be super easy to setup an equivalent... but how can a user point to such a repo hosted in GitHub?

There doesn't seem to be much info on the web about hosting a private AUR. Maybe these two tools can help (I need to investigate it a little more).

• https://github.com/pacman-repo-builder/pacman-repo-builder
• https://github.com/pacman-repo-builder/action

[hilts-vaughan]

I wish I had more information to offer, sorry. I just consumed a few for a while (AUR helpers used to use them, archlinux.fr had one for some time) Given there is tooling, obviously some people maintain them as well.. but setting up an entire package repo for a few files seems like a lot of work an infrastructure for you to have to maintain. :(

It's pretty trivial for users to point their CLI tool at a PKGBUILD though -- so even that would be helpful (though again, easy to point it at the artfact too) but without the other repo bits you don't get auto update.

[ReenigneArcher]

It looks like it actually won't be all that difficult. Here's an example. https://github.com/KSXGitHub/pacman-repo

I will play with it more in the coming days.

[ReenigneArcher]

@hilts-vaughan I have created a self hosted pacman repo, here: https://github.com/LizardByte/pacman-repo

It contains PKGBUILDs and rebuilds packages once a day, so users shouldn't even necessarily need the PKGBUILD anymore.

[patod01]

@ReenigneArcher Hi! I've been looking forward the next release since I saw the new feature of naming and deleting clients one by one. I'm a new linux user running away from windows and I chose arch like 5 months ago.

Today I was in this repository again to read the pre-releases notes once again and I just found a "read more" link, then I found out the AUR drama and it made me stare at the horizon for a while after reading all the messages there.

I don't know if this is the best place to write to you, but I just wanted to say thanks for your work. It makes me a bit sad the results of the discussion, but if you're better now, that's great. And, being positive, you motivated me to make my own repo once I learn to program well enough and have some projects! Because, certainly I enjoy pacman way more than apt, so if I change distro in the future, I'll keep using it.

I will be switching to your pacman repo next sunday. Waiting for the next stable release of this project has been like waiting for xmas for me. I can't stop reading the changelog every week. Thanks again and have a nice weekend!

[ReenigneArcher]

Thank you. The next stable release will "probably" be coming soon-ish. With that said, beta/pre-releases are usually pretty solid. Beta is also available in https://github.com/LizardByte/pacman-repo

[ReenigneArcher]

Description

Dropping support for ArchLinux AUR as I am not willing to constantly battle people like @xiota, @dr460nf1r3. No bug reports will be accepted from users using any AUR package.

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 8.99%. Comparing base (5cea1e1) to head (cd097e3).
Report is 136 commits behind head on master.

Additional details and impacted files

@@ Coverage Diff @@## master #2819 +/- ##
======================================
Coverage 8.98% 8.99% ======================================
Files 95 95 Lines 17304 17310 +6 Branches 8232 8234 +2 ======================================
+ Hits 1555 1557 +2 - Misses 12884 12888 +4 
Partials 2865 2865 

Flag	Coverage Δ
Linux	6.80% <ø> (+0.01%)	⬆️
Windows	4.16% <ø> (-0.01%)	⬇️
macOS-12	10.10% <ø> (+<0.01%)	⬆️
macOS-13	10.02% <ø> (+<0.01%)	⬆️
macOS-14	10.31% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[hilts-vaughan]

Has LizardByte considered setting up their own repository? It would allow more control and less harassment. However, I understand it is easier to simply not support it.

Thanks for at least providing a manual install option. I personally will be removing the AUR package as I can't in good faith trust someone who is willing to usurp a package like that when the upstream maintainer was doing it for so long.

Thanks for everything!

[ReenigneArcher]

@hilts-vaughan I was looking into that, although the repo would just be the 2-3 files that are in the new sunshine.pkg.tar.gz release asset.

I guess the advantage would be for the user when it comes to updates, so I will try to come up a with a way to do this, and keep things hosted on GitHub. I do see AUR has a mirror on GitHub, for which it would be super easy to setup an equivalent... but how can a user point to such a repo hosted in GitHub?

There doesn't seem to be much info on the web about hosting a private AUR. Maybe these two tools can help (I need to investigate it a little more).

• https://github.com/pacman-repo-builder/pacman-repo-builder
• https://github.com/pacman-repo-builder/action

[hilts-vaughan]

I wish I had more information to offer, sorry. I just consumed a few for a while (AUR helpers used to use them, archlinux.fr had one for some time) Given there is tooling, obviously some people maintain them as well.. but setting up an entire package repo for a few files seems like a lot of work an infrastructure for you to have to maintain. :(

It's pretty trivial for users to point their CLI tool at a PKGBUILD though -- so even that would be helpful (though again, easy to point it at the artfact too) but without the other repo bits you don't get auto update.

[ReenigneArcher]

It looks like it actually won't be all that difficult. Here's an example. https://github.com/KSXGitHub/pacman-repo

I will play with it more in the coming days.

[ReenigneArcher]

@hilts-vaughan I have created a self hosted pacman repo, here: https://github.com/LizardByte/pacman-repo

It contains PKGBUILDs and rebuilds packages once a day, so users shouldn't even necessarily need the PKGBUILD anymore.

[patod01]

@ReenigneArcher Hi! I've been looking forward the next release since I saw the new feature of naming and deleting clients one by one. I'm a new linux user running away from windows and I chose arch like 5 months ago.

Today I was in this repository again to read the pre-releases notes once again and I just found a "read more" link, then I found out the AUR drama and it made me stare at the horizon for a while after reading all the messages there.

I don't know if this is the best place to write to you, but I just wanted to say thanks for your work. It makes me a bit sad the results of the discussion, but if you're better now, that's great. And, being positive, you motivated me to make my own repo once I learn to program well enough and have some projects! Because, certainly I enjoy pacman way more than apt, so if I change distro in the future, I'll keep using it.

I will be switching to your pacman repo next sunday. Waiting for the next stable release of this project has been like waiting for xmas for me. I can't stop reading the changelog every week. Thanks again and have a nice weekend!

[ReenigneArcher]

Thank you. The next stable release will "probably" be coming soon-ish. With that said, beta/pre-releases are usually pretty solid. Beta is also available in https://github.com/LizardByte/pacman-repo

[ReenigneArcher]

Description

Dropping support for ArchLinux AUR as I am not willing to constantly battle people like @xiota, @dr460nf1r3. No bug reports will be accepted from users using any AUR package.

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 8.99%. Comparing base (5cea1e1) to head (cd097e3).
Report is 136 commits behind head on master.

Additional details and impacted files

@@ Coverage Diff @@## master #2819 +/- ##
======================================
Coverage 8.98% 8.99% ======================================
Files 95 95 Lines 17304 17310 +6 Branches 8232 8234 +2 ======================================
+ Hits 1555 1557 +2 - Misses 12884 12888 +4 
Partials 2865 2865 

Flag	Coverage Δ
Linux	6.80% <ø> (+0.01%)	⬆️
Windows	4.16% <ø> (-0.01%)	⬇️
macOS-12	10.10% <ø> (+<0.01%)	⬆️
macOS-13	10.02% <ø> (+<0.01%)	⬆️
macOS-14	10.31% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[hilts-vaughan]

Has LizardByte considered setting up their own repository? It would allow more control and less harassment. However, I understand it is easier to simply not support it.

Thanks for at least providing a manual install option. I personally will be removing the AUR package as I can't in good faith trust someone who is willing to usurp a package like that when the upstream maintainer was doing it for so long.

Thanks for everything!

[ReenigneArcher]

@hilts-vaughan I was looking into that, although the repo would just be the 2-3 files that are in the new sunshine.pkg.tar.gz release asset.

I guess the advantage would be for the user when it comes to updates, so I will try to come up a with a way to do this, and keep things hosted on GitHub. I do see AUR has a mirror on GitHub, for which it would be super easy to setup an equivalent... but how can a user point to such a repo hosted in GitHub?

There doesn't seem to be much info on the web about hosting a private AUR. Maybe these two tools can help (I need to investigate it a little more).

• https://github.com/pacman-repo-builder/pacman-repo-builder
• https://github.com/pacman-repo-builder/action

[hilts-vaughan]

I wish I had more information to offer, sorry. I just consumed a few for a while (AUR helpers used to use them, archlinux.fr had one for some time) Given there is tooling, obviously some people maintain them as well.. but setting up an entire package repo for a few files seems like a lot of work an infrastructure for you to have to maintain. :(

It's pretty trivial for users to point their CLI tool at a PKGBUILD though -- so even that would be helpful (though again, easy to point it at the artfact too) but without the other repo bits you don't get auto update.

[ReenigneArcher]

It looks like it actually won't be all that difficult. Here's an example. https://github.com/KSXGitHub/pacman-repo

I will play with it more in the coming days.

[ReenigneArcher]

@hilts-vaughan I have created a self hosted pacman repo, here: https://github.com/LizardByte/pacman-repo

It contains PKGBUILDs and rebuilds packages once a day, so users shouldn't even necessarily need the PKGBUILD anymore.

[patod01]

@ReenigneArcher Hi! I've been looking forward the next release since I saw the new feature of naming and deleting clients one by one. I'm a new linux user running away from windows and I chose arch like 5 months ago.

Today I was in this repository again to read the pre-releases notes once again and I just found a "read more" link, then I found out the AUR drama and it made me stare at the horizon for a while after reading all the messages there.

I don't know if this is the best place to write to you, but I just wanted to say thanks for your work. It makes me a bit sad the results of the discussion, but if you're better now, that's great. And, being positive, you motivated me to make my own repo once I learn to program well enough and have some projects! Because, certainly I enjoy pacman way more than apt, so if I change distro in the future, I'll keep using it.

I will be switching to your pacman repo next sunday. Waiting for the next stable release of this project has been like waiting for xmas for me. I can't stop reading the changelog every week. Thanks again and have a nice weekend!

[ReenigneArcher]

Thank you. The next stable release will "probably" be coming soon-ish. With that said, beta/pre-releases are usually pretty solid. Beta is also available in https://github.com/LizardByte/pacman-repo

[ReenigneArcher]

Description

Dropping support for ArchLinux AUR as I am not willing to constantly battle people like @xiota, @dr460nf1r3. No bug reports will be accepted from users using any AUR package.

Screenshot

Issues Fixed or Closed

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Dependency update (updates to dependencies)
• Documentation update (changes to documentation)
• Repository update (changes to repository files, e.g. .github/...)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

• I want maintainers to keep my branch updated

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 8.99%. Comparing base (5cea1e1) to head (cd097e3).
Report is 136 commits behind head on master.

Additional details and impacted files

@@ Coverage Diff @@## master #2819 +/- ##
======================================
Coverage 8.98% 8.99% ======================================
Files 95 95 Lines 17304 17310 +6 Branches 8232 8234 +2 ======================================
+ Hits 1555 1557 +2 - Misses 12884 12888 +4 
Partials 2865 2865 

Flag	Coverage Δ
Linux	6.80% <ø> (+0.01%)	⬆️
Windows	4.16% <ø> (-0.01%)	⬇️
macOS-12	10.10% <ø> (+<0.01%)	⬆️
macOS-13	10.02% <ø> (+<0.01%)	⬆️
macOS-14	10.31% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[hilts-vaughan]

Has LizardByte considered setting up their own repository? It would allow more control and less harassment. However, I understand it is easier to simply not support it.

Thanks for at least providing a manual install option. I personally will be removing the AUR package as I can't in good faith trust someone who is willing to usurp a package like that when the upstream maintainer was doing it for so long.

Thanks for everything!

[ReenigneArcher]

@hilts-vaughan I was looking into that, although the repo would just be the 2-3 files that are in the new sunshine.pkg.tar.gz release asset.

I guess the advantage would be for the user when it comes to updates, so I will try to come up a with a way to do this, and keep things hosted on GitHub. I do see AUR has a mirror on GitHub, for which it would be super easy to setup an equivalent... but how can a user point to such a repo hosted in GitHub?

There doesn't seem to be much info on the web about hosting a private AUR. Maybe these two tools can help (I need to investigate it a little more).

• https://github.com/pacman-repo-builder/pacman-repo-builder
• https://github.com/pacman-repo-builder/action

[hilts-vaughan]

I wish I had more information to offer, sorry. I just consumed a few for a while (AUR helpers used to use them, archlinux.fr had one for some time) Given there is tooling, obviously some people maintain them as well.. but setting up an entire package repo for a few files seems like a lot of work an infrastructure for you to have to maintain. :(

It's pretty trivial for users to point their CLI tool at a PKGBUILD though -- so even that would be helpful (though again, easy to point it at the artfact too) but without the other repo bits you don't get auto update.

[ReenigneArcher]

It looks like it actually won't be all that difficult. Here's an example. https://github.com/KSXGitHub/pacman-repo

I will play with it more in the coming days.

[ReenigneArcher]

@hilts-vaughan I have created a self hosted pacman repo, here: https://github.com/LizardByte/pacman-repo

It contains PKGBUILDs and rebuilds packages once a day, so users shouldn't even necessarily need the PKGBUILD anymore.

[patod01]

@ReenigneArcher Hi! I've been looking forward the next release since I saw the new feature of naming and deleting clients one by one. I'm a new linux user running away from windows and I chose arch like 5 months ago.

Today I was in this repository again to read the pre-releases notes once again and I just found a "read more" link, then I found out the AUR drama and it made me stare at the horizon for a while after reading all the messages there.

I don't know if this is the best place to write to you, but I just wanted to say thanks for your work. It makes me a bit sad the results of the discussion, but if you're better now, that's great. And, being positive, you motivated me to make my own repo once I learn to program well enough and have some projects! Because, certainly I enjoy pacman way more than apt, so if I change distro in the future, I'll keep using it.

I will be switching to your pacman repo next sunday. Waiting for the next stable release of this project has been like waiting for xmas for me. I can't stop reading the changelog every week. Thanks again and have a nice weekend!

[ReenigneArcher]

Thank you. The next stable release will "probably" be coming soon-ish. With that said, beta/pre-releases are usually pretty solid. Beta is also available in https://github.com/LizardByte/pacman-repo