doctl package for Fedora

[Dusty Mabe]

Anyone interested in packaging up Digital Ocean's CLI for Fedora?

https://github.com/digitalocean/doctl

Dusty

[Dharmit Shah]

Hi,

I'm interested in working on this. I'll go through the pointers you provided to me
on #fedora-cloud IRC channel and get back to the list/channel with queries.

Regards,
Dharmit.

[Dharmit Shah]

Hi,

After setting up gofed on my system, I did:

$ gofed repo2spec --detect https://github.com/digitalocean/doctl
--commit bb6a9630426adc1fed74f93df6f749deae6530aa

since that's the commit ID for latest version - 1.6.0.

After that I did:

$ gofed fetch --spec

to download the tarball.

Doing a local build or mockbuild is failing. In case of local build,
it's throwing [1] while for mockbuild I'm seeing this [2].

For both cases, it seems to me like missing Go dependencies are the
issue. How am I supposed to make these dependencies available?

Also, just want to know if I'm following the right steps. The specfile
generated by repo2spec command is intimidating!

[1] https://paste.fedoraproject.org/paste/P-t~p-RmBzpVb8nl0avICF5M1UNdIGYhyRL...
[2] https://paste.fedoraproject.org/paste/WkcqyLNWkfuysR0OUpsrdl5M1UNdIGYhyRL...

Regards,
Dharmit.

On 18 April 2017 at 21:58, Dharmit Shah <shahdharmit(a)gmail.com&gt; wrote:
> Hi,
>
> I'm interested in working on this. I'll go through the pointers you provided
to me on #fedora-cloud IRC channel and get back to the list/channel with queries.
>
> Regards,
> Dharmit.
> _______________________________________________
> cloud mailing list -- cloud(a)lists.fedoraproject.org
> To unsubscribe send an email to cloud-leave(a)lists.fedoraproject.org

[Dusty Mabe]

On 04/22/2017 10:31 AM, Dharmit Shah wrote:
>  Hi, 
Hey Dharmit,

Thanks for working on this!

>  
>  After setting up gofed on my system, I did:
>  
>  $ gofed repo2spec --detect https://github.com/digitalocean/doctl
>  --commit bb6a9630426adc1fed74f93df6f749deae6530aa
>  
>  since that's the commit ID for latest version - 1.6.0.
>  
>  After that I did:
>  
>  $ gofed fetch --spec
>  
>  to download the tarball.
>  
>  Doing a local build or mockbuild is failing. In case of local build,
>  it's throwing [1] while for mockbuild I'm seeing this [2]. 
So there are two ways to build go packages in Fedora. One is to build
from the source of a bunch of devel packages that have already been
packaged up for Fedora. The other is to "bundle" all of that stuff and
essentially provide the source for all of those deps within this
package itself.

I believe it is preferable to build from the source of all the devel
packages that are already a part of Fedora, but that is the long/hard
approach because we have to package up the source files into devel
rpms for all of them. It's not really hard to do this, and would be
great if you did, but not required. An example of bundling the source
code is here:

https://bugzilla.redhat.com/show_bug.cgi?id=1418368

If you want to bundle instead, an example is the kompose rpm here:

https://src.fedoraproject.org/cgit/rpms/kompose.git/tree/

You can do a diff between kompose.spec and kompose.spec.orig to see
what changes were made. Also, check out the notes.txt file.

>  
>  For both cases, it seems to me like missing Go dependencies are the
>  issue. How am I supposed to make these dependencies available?
>  
>  Also, just want to know if I'm following the right steps. The specfile
>  generated by repo2spec command is intimidating! 
It can be :). We'll help you through it!

> 
> [1]
https://paste.fedoraproject.org/paste/P-t~p-RmBzpVb8nl0avICF5M1UNdIGYhyRL...
> [2]
https://paste.fedoraproject.org/paste/WkcqyLNWkfuysR0OUpsrdl5M1UNdIGYhyRL...
> 
> Regards,
> Dharmit.

[Kushal Das]

On 23/04/17, Dusty Mabe wrote:
>  
>  
>  On 04/22/2017 10:31 AM, Dharmit Shah wrote:
>  > Hi,
>  
>  Hey Dharmit,
>  
>  Thanks for working on this!
>  
>  > 
>  > After setting up gofed on my system, I did:
>  > 
>  > $ gofed repo2spec --detect https://github.com/digitalocean/doctl
>  > --commit bb6a9630426adc1fed74f93df6f749deae6530aa
>  > 
>  > since that's the commit ID for latest version - 1.6.0.
>  > 
>  > After that I did:
>  > 
>  > $ gofed fetch --spec
>  > 
>  > to download the tarball.
>  > 
>  > Doing a local build or mockbuild is failing. In case of local build,
>  > it's throwing [1] while for mockbuild I'm seeing this [2].
>  
>  So there are two ways to build go packages in Fedora. One is to build
>  from the source of a bunch of devel packages that have already been
>  packaged up for Fedora. The other is to "bundle" all of that stuff and
>  essentially provide the source for all of those deps within this
>  package itself.
>  
>  I believe it is preferable to build from the source of all the devel
>  packages that are already a part of Fedora, but that is the long/hard
>  approach because we have to package up the source files into devel
>  rpms for all of them. It's not really hard to do this, and would be
>  great if you did, but not required. An example of bundling the source
>  code is here:
>  
>  https://bugzilla.redhat.com/show_bug.cgi?id=1418368
>  
>  If you want to bundle instead, an example is the kompose rpm here:
>  
>  https://src.fedoraproject.org/cgit/rpms/kompose.git/tree/
>   
Also have a look at the gotun review [1], where I also started with the
gofed generated spec, and then changed for the dependencies as Jan
helped to do package the deps.


[1] https://bugzilla.redhat.com/show_bug.cgi?id=1386625

Kushal

>  You can do a diff between kompose.spec and kompose.spec.orig to see
>  what changes were made. Also, check out the notes.txt file.
>  
>  > 
>  > For both cases, it seems to me like missing Go dependencies are the
>  > issue. How am I supposed to make these dependencies available?
>  > 
>  > Also, just want to know if I'm following the right steps. The specfile
>  > generated by repo2spec command is intimidating!
>  
>  It can be :). We'll help you through it!
>  
>  > 
>  > [1]
> https://paste.fedoraproject.org/paste/P-t~p-RmBzpVb8nl0avICF5M1UNdIGYhyRL...
>  > [2]
> https://paste.fedoraproject.org/paste/WkcqyLNWkfuysR0OUpsrdl5M1UNdIGYhyRL...
>  > 
>  > Regards,
>  > Dharmit.
>  _______________________________________________
>  cloud mailing list -- cloud(a)lists.fedoraproject.org
>  To unsubscribe send an email to cloud-leave(a)lists.fedoraproject.org 
-- 
Fedora Cloud Engineer
CPython Core Developer
https://kushaldas.in
https://dgplug.org

[Jan Chaloupka]

Hi Dharmit,

>  The specfile generated by repo2spec command is intimidating! 
Yeah, we are still working on simplifying the spec file.

The spec file generator only generates the spec file. It does not handle dependencies. It
is up to a package to generate spec files for all the required dependencies (if they are
not already in the distro), resp. update all outdated ones.

As another step I would recommend to open a review request in Bugzilla [1] for the
generated spec file of yours and CC me. So we can continue the discussion there with the
concrete project. 

[1] https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&format=fedor...

Regards
Jan

[Dusty Mabe]

On 04/24/2017 04:24 AM, Jan Chaloupka wrote:
>  Hi Dharmit,
>  
> > The specfile generated by repo2spec command is intimidating!
>  
>  Yeah, we are still working on simplifying the spec file.
>  
>  The spec file generator only generates the spec file. It does not handle dependencies. It
> is up to a package to generate spec files for all the required dependencies (if they are
> not already in the distro), resp. update all outdated ones.
>  
>  As another step I would recommend to open a review request in Bugzilla [1] for the
> generated spec file of yours and CC me. So we can continue the discussion there with the
> concrete project.  
Hey Dharmit,

Can you go ahead and post up a BZ for review and we can start to get
the spec file in working order?

> 
> [1]
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&format=fedor...
> 
> Regards
> Jan
> _______________________________________________
> cloud mailing list -- cloud(a)lists.fedoraproject.org
> To unsubscribe send an email to cloud-leave(a)lists.fedoraproject.org
>

[Dharmit Shah]

Hi Dusty,

On 14 May 2017 at 05:11, Dusty Mabe <dusty(a)dustymabe.com&gt; wrote:
>  Hey Dharmit,
>
>  Can you go ahead and post up a BZ for review and we can start to get
>  the spec file in working order?
>  
I've opened a BZ to get started with this:
https://bugzilla.redhat.com/show_bug.cgi?id=1452155

Regards,
Dharmit.