Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Adds fpm-recipe for package #716
So, I've made a basic proof-of-concept automated package building pipeline using fpm-cookery and werker:
Example of created RPM build:
This uses a docker image for CentOS, creates a package and would be able to push it up to https://PackageCloud.io using an API token
The ideal end use-case would be proper addition to upstream repositories, and I'm looking into the Debian process to do this, but it's a lot more difficult than this minimum viable packaging
@ncw I'd like to get your view on this
Some basic questions:
Sorry I haven't commented on this - it had somehow escaped my attention!
I am interested in building OS packages - it is one of those things I've never quite found the time for.
To be part of a major distro, I need to make rclone build repeatably from source #816. Once I do that I could upload rclone to launchpad and that would make .deb builds for ubuntu (and debian based distributions). I don't know very much about centos/rpm based distros though - is there something similar to a ppa for Centos?
I see your solution repackages the released zip files which is a great idea, but won't fly with the distro vendors.
Not quite sure I understand what you mean. Do you mean adding the .deb/.rpm files to the download page - that sounds good to me.
In an ideal world as part of the build process I'd build .deb/.rpm packages too.
I see they do open source projects - maybe they would do it for free? I'm not keen on the rclone project incurring fees if I can avoid it. I've asked them
Ultimately if the upstream distros package rclone then they will do their own specfiles, so fpm seems like a reasonable solution in the mean time.
I think your pull request is missing some bits to actually do the build isn't it? Can you add those and then I'll give it all a try!
packagecloud.io have agreed to give rclone a free account under these conditions, which seem reasonable to me
So we are all go!
Sorry, I've dropped the ball on this pull request!
Do you still want to merge it?
rclone has gained a couple of extra packaging options since you submitted this - a snap and a packager.io build (which I'm not totally happy with).
If so can you rebase it please? There are quite a few conflicts in the docs...
At minimum if you could send me a pull request with details of the brew formula for OS X that would be great!
@ncw I was thinking of submitting an FPM pull request with automated building / pushing to packagecloud. Would you still find this at all useful? I still think it would be nice to just add a repo and have rclone updated when I run
@CorbanR - apologies for the delay in replying!
Can you explain in a bit more depth what your plan involves? Which bits need to go in the rclone repo and which don't?
As I understand it FPM would build rclone into .deb and .rpm files for me. I've been investigating nfpm for this purpose too - it would be very easy to fit in the build process.
packagecloud then makes an apt and yum repository.
I'm reluctant to take too much packaging stuff into the rclone repo as I'm not an expert and it distracts me from my primary purpose of making rclone! We did have snap packaging in the rclone repo, but I had to take it out as I couldn't get it to work properly and the originally submitter couldn't help either.
@ncw no worries!. I was planning on just using
ill push up a POC of what I was thinking to a separate repo and link once complete. It may make sense to keep all of this in a separate repo.
Anyway, ill post a link once i have a POC and you can decide where it should live if you think it's useful.