Hi all,
I'd like to have rubygem-fluent-plugin-rewrite-tag-filter in the opstools sig repos.
Not sure what exactly should be done for this.
There are two github organizations, [1] and [2], and some packages forked between them.
Seems like we have a repo per project. So we need a new project, right? In which organization? Who can/should handle this?
I currently try to use a build I found in copr [3], and it seems to work. I checked the git repo [4] it was built from, and the spec file there is an unchanged output of gem2rpm. We can start with this, I didn't review it yet myself (and have zero experience with packaging ruby gems).
Thanks and best regards,
[1] https://github.com/opstools-packages [2] https://github.com/centos-opstools [3] https://copr.fedorainfracloud.org/coprs/a15/fluent-0.12/build/469721/ [4] http://copr-dist-git.fedorainfracloud.org/cgit/a15/fluent-0.12/rubygem-fluen...
On 06/12/16 09:41, Yedidyah Bar David wrote:
Hi all,
I'd like to have rubygem-fluent-plugin-rewrite-tag-filter in the opstools sig repos.
Not sure what exactly should be done for this.
There are two github organizations, [1] and [2], and some packages forked between them.
Seems like we have a repo per project. So we need a new project, right? In which organization? Who can/should handle this?
I currently try to use a build I found in copr [3], and it seems to work. I checked the git repo [4] it was built from, and the spec file there is an unchanged output of gem2rpm. We can start with this, I didn't review it yet myself (and have zero experience with packaging ruby gems).
Thanks and best regards,
Hello Didi,
First, we'd need to make sure, the package is acceptable (i.e. it's licensed by an acceptable license). If the package is compatible with Fedora guidelines, we're good.
The repository itself will be created on [5], and will be mirrored to [2]. Once the package is included there, we can issue a build.
Matthias
[1] https://github.com/opstools-packages [2] https://github.com/centos-opstools [3] https://copr.fedorainfracloud.org/coprs/a15/fluent-0.12/build/469721/ [4] http://copr-dist-git.fedorainfracloud.org/cgit/a15/fluent-0.12/rubygem-fluen...
On Tue, Dec 6, 2016 at 12:04 PM, Matthias Runge mrunge@matthias-runge.de wrote:
On 06/12/16 09:41, Yedidyah Bar David wrote:
Hi all,
I'd like to have rubygem-fluent-plugin-rewrite-tag-filter in the opstools sig repos.
Not sure what exactly should be done for this.
There are two github organizations, [1] and [2], and some packages forked between them.
Seems like we have a repo per project. So we need a new project, right? In which organization? Who can/should handle this?
I currently try to use a build I found in copr [3], and it seems to work. I checked the git repo [4] it was built from, and the spec file there is an unchanged output of gem2rpm. We can start with this, I didn't review it yet myself (and have zero experience with packaging ruby gems).
Thanks and best regards,
Hello Didi,
First, we'd need to make sure, the package is acceptable (i.e. it's licensed by an acceptable license). If the package is compatible with Fedora guidelines, we're good.
The upstream source says it's ASL 2.0:
https://github.com/fluent/fluent-plugin-rewrite-tag-filter/blob/master/LICEN...
The repository itself will be created on [5], and will be mirrored to [2]. Once the package is included there, we can issue a build.
[5] ?
Thanks,
Matthias
[1] https://github.com/opstools-packages [2] https://github.com/centos-opstools [3] https://copr.fedorainfracloud.org/coprs/a15/fluent-0.12/build/469721/ [4] http://copr-dist-git.fedorainfracloud.org/cgit/a15/fluent-0.12/rubygem-fluen...
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 06/12/16 11:33, Yedidyah Bar David wrote:
On Tue, Dec 6, 2016 at 12:04 PM, Matthias Runge
First, we'd need to make sure, the package is acceptable (i.e. it's licensed by an acceptable license). If the package is compatible with Fedora guidelines, we're good.
The upstream source says it's ASL 2.0:
https://github.com/fluent/fluent-plugin-rewrite-tag-filter/blob/master/LICEN...
The repository itself will be created on [5], and will be mirrored to [2]. Once the package is included there, we can issue a build.
[5] ?
eh, sorry.
[5] https://review.rdoproject.org/r/#/q/status:open
What upstream states is good for a starter. Fedora guidelines[6] are a bit more detailed.
[6] https://fedoraproject.org/wiki/Packaging:ReviewGuidelines
Matthias
-
Matthias Runge -
Yedidyah Bar David