Bug #2123: Package name mismatch: foreman-fog vs foreman-ec2 - Packaging - Foreman

Custom queries

All issues closed in the last 3 weeks
Easy and Trivial Issues
Good first issues - Foreman core
Mine
My issues closed in the last 3 weeks
Untriaged and opened in the past two weeks

Actions

Copy link

Bug #2123

closed

Package name mismatch: foreman-fog vs foreman-ec2

Added by Dominic Cleal over 11 years ago. Updated about 11 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Dominic Cleal

Category:

Target version:

1.2

Difficulty:

Triaged:

Bugzilla link:

Pull request:

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

The Debian package for EC2 and Fog support is "foreman-fog", while the RPM package is "foreman-ec2". One of these should change for consistency in documentation etc. I'd suggest foreman-ec2 is correct, since it's self-explanatory as to what functionality it adds.

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Greg Sutcliffe over 11 years ago

I disagree. The fog packages are required for other compute resources (such as libvirt) and it then becomes non-intuitve as to why foreman-libvirt or foreman-vmware depends on foreman-ec2.

I have no issue with the supported technologies being listed in the description fields (which they are for debs), which is the correct place to list further information about what the package does.

Actions

Copy link

Updated by Greg Sutcliffe over 11 years ago

Status changed from New to Need more information

Actions

Copy link

Updated by Dominic Cleal over 11 years ago

That makes sense, so I think -fog would be better than -ec2. Is "foreman-compute" any clearer?

Actions

Copy link

Updated by Greg Sutcliffe over 11 years ago

The only thing it installs is "bundler.d/fog.rb" which only contains the fog gem. So I think it's ideally named as it is :)

Actions

Copy link

Updated by Sam Kottler over 11 years ago

I think both packages should be named foreman-compute, but at the very least they should be named the same thing. I think foreman-ec2 isn't a good name because then I'd expect a foreman-libvirt, foreman-ovirt, foreman-openstack, etc, but those don't exist. As a new user, I'd go for the foreman-compute package before foreman-fog. Just my $.02.

Actions

Copy link

Updated by Greg Sutcliffe over 11 years ago

Ok, i can run with that. I'll make the change in the next round of RC packages. Fortunately debs have an easy way to rename packages as part of an upgrade :)

Actions

Copy link