Packaging PiCloud
Amit Saha
I have been playing around with PiCloud and greatly impressed by the
ease of use. Great job!
To include PiCloud client in the Fedora Scientific Spin
(http://spins.fedoraproject.org/scientific-kde/) I am planning to
package PiCloud for Fedora Linux.
Shall I just take the latest available source code from PyPi
(http://pypi.python.org/pypi/cloud) and use it for the package?
I would appreciate any information on this.
Best,
Amit
Ken Elkabany
Amit Saha
On 02/21/2012 05:12 PM, Ken Elkabany wrote:
> Hi Amit,
>
> Thanks for taking the initiative! Yes, feel free to take the latest
> source code from PyPI. How often are new versions of Fedora Scientific
> Spin released? Our client library gets updated quite often.
Thank you for your reply. Fedora Scientific is released every six months
-- i.e official Fedora release cycle. I hope to create the package and
maintain it as well. So, I shall try to keep the library updated.
I am working to create the package -- shall keep the list updated.
Best,
Amit
>
> Best,
> Ken
>
> On Mon, Feb 20, 2012 at 2:17 AM, Amit Saha <echo...@gmail.com
> <mailto:echo...@gmail.com>> wrote:
>
> Hello:
>
> I have been playing around with PiCloud and greatly impressed by the
> ease of use. Great job!
>
> To include PiCloud client in the Fedora Scientific Spin
> (http://spins.fedoraproject.org/scientific-kde/) I am planning to
> package PiCloud for Fedora Linux.
> Shall I just take the latest available source code from PyPi
> (http://pypi.python.org/pypi/cloud) and use it for the package?
>
> I would appreciate any information on this.
>
> Best,
> Amit
>
> --
> http://echorand.me
>
>
Ken Elkabany
Amit Saha
On Wed, Feb 22, 2012 at 12:08 PM, Ken Elkabany <k...@picloud.com> wrote:
> Sounds great. Let us know if you have any issues. Thanks again!
Okay, so I have got a preliminary RPM ready and it seems to work
correctly. Like I mentioned in another email, I have also created a
man page for it and I have created the RPM such that it also installs
the man page for the CLI: picloud.
However, to enable this: I had to make two changes to the PiCloud sources:
1. Create a directory 'doc' which will store the manual page
1. Modify setup.py to include this data directory in the data_files[ ]
so that it gets copied to the /usr/share/man upon python setup.py
install
Now, before I submit the RPM package for review to Fedora, it would be
desirable if the PiCloud source code would have these changes. Do you
think that's possible? If that's not possible for now -- then I will
have to go ahead without the man page and wait till the next release
for that.
Kindly let me know your thoughts. Please let me know if you are
interested in trying out the RPM.
Best,
-Amit
Ken Elkabany
Aaron Staley
Amit Saha
On Sat, Feb 25, 2012 at 6:55 PM, Aaron Staley <aa...@picloud.com> wrote:
> Hi Amit,
>
> Excellent work. We can incorporate your changes in the next client release.
> Could you email me your changes? I'd also love to put your man page in our
> distribution if that'd be cool.
Thank you for your reply. The changes that I propose are:
- create a doc/ sub-directory in the source tarball and put the
source for the man page there (please find it attached)
(so, the man page will always be released with the source code from now on)
- Add this to setup.py: ((just before entry_points)
data_files=[('/usr/share/man/man1', ['doc/picloud.1'])],
When would be the next client release? I have my RPM ready and was
planning to submit it for review to Fedora -- but if I was to include
the man page then, the client release has to be soon (asap, at the
risk of sounding demanding:-)) . Is that possible?
> The man page itself looks great; I should note that some files in our
> package are under less restrictive licenses than the LGPL (as described in
> PiCloud's LICENSE).
Yes, I have noted that in the package .spec file as well. And so, I
just point to the LICENSE file in the man page.
Kindly let me know if you would require further information.
Best,
Amit
Aaron Staley
Amit Saha
On Tue, Feb 28, 2012 at 5:42 PM, Aaron Staley <aa...@picloud.com> wrote:
> Hi Amit,
>
> Thanks a lot for getting back to me. The changes will be easy to make and I
> hope to have a new client out by Thursday.
That sounds great! Thanks a lot.
> One unfortunate aspect of manpages is that there appear to be no standard
> location across unix flavors. Fedora and Ubuntu appears to both keep them
> in /usr/share/man/.. so this simple copying should work for most of our
> users.. Incidentally, does Fedora store manpages uncompressed? In debian
> derivatives, they tend to be gzipped (though they work fine if not
> compressed).
I just checked and what I saw is that the the picloud.1 file, its
actually stored as picloud.1.gz in the /usr/share/man/man1 directory.
So I guess we are cool.
>
> Finally, with your permission, could I modify the man page AUTHOR section as
> follows?
>
> picloud package developed by PiCloud team (http://www.picloud.com)
> This manual page was written by Amit Saha (amits...@gmail.com).
Please go ahead and do that. Could you please replace my email as:
amit...@fedoraproject.org ? (I just wanted to give you guys credit
for doing all the documentation :-))
>
> (Feel free to keep the AUTHOR section as is in your RPM).
Sorry if I misunderstood this -- the RPM will take the man page from
the source package -- the above AUTHOR section is just fine. Pls.
correct me if I misunderstood.
So, I shall wait for the new client release -- finalize the RPM and
submit for review. Great.
Do let me know if there is anything else.
Best,
-Amit
Amit Saha
Just a quick note: Please also feel free to modify the LICENSE section
to make it more appropriate and correct.
And, besides the official Fedora package, I am hoping to use the
OpenSUSE build service to maintain packages for other distros as well.
But, let's first get the first out of the way.
Best,
Amit
Ken Elkabany
Amit Saha
On Tue, Feb 28, 2012 at 6:56 PM, Ken Elkabany <k...@picloud.com> wrote:
> Hi Amit,
>
> Will it be possible to regularly (every month) update the version of the
> cloud client in the Fedora repositories? We update the cloud client often,
> and it would be great if it wasn't constrained to a 6-month release cycle on
> Fedora.
This will be my first package for Fedora -- but, I am pretty sure I
can update the RPMs whenever upstream (PiCloud) has a new release [1].
So it won't be restricted by the 6-month release cycle. Users can just
do a upgrade and they will get a upgraded client.
And as far as I am concerned, I will do my best to always keep the
package updated -- a day or two lag may be, but not more than that.
Kindly let me know if you have any other queries.
[1] http://fedoraproject.org/wiki/Upstream_Release_Monitoring
Best,
Amit
Aaron Staley
Amit Saha
On 03/04/2012 09:24 PM, Aaron Staley wrote:
> Hi Amit,
>
> The new cloud 2.4.2 is out
> I couldn't use data_files, as the script crashes if the destination path
> is not writable.
> Instead, the script, when run in 'install' mode, just manually copies
> the file and warns if the copy was not possible.
Sure. I took care of in the new SPEC file. I have filed the package for
a review with Fedora [1]. I shall keep the list updated.
Many thanks for getting the client out!
1. https://bugzilla.redhat.com/show_bug.cgi?id=799810
-Amit