[SOLVED] EBuilds for Barrier v2.4.0

[gjy0724]

I am hoping that someone still has the ebuilds (app plus two patches) for barrier v2.4.0.

‎x11-misc/barrier/barrier-2.4.0.ebuild
‎x11-misc/barrier/files/barrier-2.4.0-gcc-13.patch
x11-misc/barrier/files/barrier-2.4.0-includes.patch‎

I am currently using barrier to utilize the keyboard and mouse on my desktop to one of my laptops...I was going to add it to my second laptop but apparently the ebuilds were removed from the repo in July and I didn't notice. I also noticed that the ebuilds for synergy were also removed. I've had better luck with barrier, but if someone has files for synergy I would give it another shot.

Thanks in advance!

[gjy0724]

Just wanted to post an update. I was able to retrieve the contents of the three files from the repos history...so much for deleting files from repos and them being completely gone from history. Now I'm just trying to add the files to my personal ebuild repo.

ebuild x11-misc/barrier/barrier-2.4.0.ebuild digest
ebuild:/path/to/x11-misc/barrier/barrier-2.4.0.ebuild: x11-misc/barrier-2.4.0: does not follow correct package syntax

If anyone has any ideas on what I am doing wrong, please let me know. In the meantime, I will keep working on the files.

[flexibeast]

pkgcheck scan can be used to do QA checks on an ebuild, but as far as i can tell, it can only be used on an ebuild appropriately located within an ebuild repo (because some of the QA checks depend on the configuration defined by the repo). If that's correct, you'd need to create an ebuild repository and work on the ebuild there.

[gjy0724]

I ran pkgcheck scan and the only thing is said about that folder was UnknownCategoryDirs: unknown category dirs: ARCHIVED, x11-misc. Then I went to the ebuild repo link you sent and looked over my process to see if Im doing it correctly. I then ran pkgdev manifest but that didnt help either. I tried rerunning the ebuild command, but got the same message. I don't have alot of experience with ebuilds. I've mainly copied them from other repos for consolidation purposes...similar to barrier, but they have all worked so far. I hope to get more proficient at it in the future but as normal...other priorities.

[gjy0724]

Okay, I found my problem. Somehow when I created the original x11-misc folder, some extra (i.e. hidden) characters were part of the x11-misc folder name. I found then when I ran git status on the repo. So I copied the folder to a temp location, recreated the x11-misc/barrier folders then copied the everything under barrier in the temp location to the newly created folder and it worked.

Thanks for the help!