I created an ebuild for AeroFS - it's rather crude: - upstream is not using version-numbers, - the ebuild uses fetch-restrictions, AeroFS is currently on invitations only. Reproducible: Always
Created attachment 281879 [details] net-p2p/aerofs-bin
Should it not rather be in net-fs/ than in net-p2p/? Also it should rely on the aerofs-x86/x86_64.tar.gz instead of the debian file. When I have more time I will submit a modified ebuild.
Created attachment 314295 [details] net-p2p/aerofs-bin Here the ebuild belonging to the tgz-version of the aerofs installer. It is difficult for versioning since there is no version in the tgz nor in other aerofs packages.
AeroFS depends on app-arch/sharutils (it uses uudecode)
Technically, the program itself does have a particular version number, but the filename does not include it (see http://support.aerofs.com/knowledgebase/articles/93285-release-notes for version history). Also, it handles updates by itself, and copies the binaries into the personal home directory to accomplish this more easily without root (similar to how Steam for Linux works).
Also, since this is technically most similar to a service like dropbox, I think net-misc/ is probably more appropriate, but that's just a guess based on where dropbox and dropbox-cli are currently sitting. It's not really a filesystem, despite the name, but is more of a synchronization helper like dropbox, but making the server storage component optional.
Created attachment 336864 [details] net-misc/aerofs-0.4.144.ebuild My ebuild certainly isn't the greatest, but it does what I need. It also includes the fix for the issue I encountered with the latest version of uudecode/sharutils (http://support.aerofs.com/forums/147816-linux-problems/suggestions/3578017-aerofs-and-arch-linux).
Created attachment 336866 [details] net-misc/aerofs-0.4.144.ebuild Sorry, my last ebuild was a bit premature. This one has a much cleaner sed solution to the (temporary) uudecode problem. I guess another solution would be to depend on any version of sharutils other than the latest offending version, but I'm not sure which way is preferred as the "Gentoo way", and would really appreciate some official input on that. Also, instead of just doing "dobin" on all the files, we now do dobin on the one file that actually contains useful content, and dosym for the other three which are symlinks in the original distribution, too.
Created attachment 336872 [details] net-misc/aerofs-0.4.144.ebuild This is my last comment/upload tonight, promise. :) This includes a quick fix to error code 127 on application launch (http://support.aerofs.com/forums/147816-linux-problems/suggestions/3135916-daemon-exited-with-code-127).
Created attachment 337378 [details] net-misc/aerofs-0.4.147.ebuild Here's an updated ebuild (just in time for the 0.4.147 version bump). The biggest change is that it now downloads aerofs-installer.tgz to aerofs-VERSION.tgz inside distfiles so that when the version gets bumped we actually get a changed Manifest correctly. I did this to follow the convention I've seen in other ebuilds in the portage tree where upstream doesn't have version numbers on their distribution files. I also changed the few places we had "aerofs" directly hard-coded to use ${PN} like they should've from the start so that we can easily copy the ebuild and rename it to aerofsts when the Team Server stuff comes out of the (even more private than AeroFS proper) private beta that it's in. In fact, the ebuild should work correctly as-is now if copied to be aerofsts, but I haven't tested that.
Not exactly an update to the ebuild, but significant for it nonetheless: as of today (version 0.4.150), the limit on invites is now lifted. Any existing user may invite an unlimited amount of other users (see http://support.aerofs.com/knowledgebase/articles/93285-release-notes).
