Project

General

Profile

Actions

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:
Category:
-
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

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.

Actions #1

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 #2

Updated by Greg Sutcliffe over 11 years ago

  • Status changed from New to Need more information
Actions #3

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 #4

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 #5

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 #6

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 #7

Updated by Greg Sutcliffe over 11 years ago

Fixed in the deb release. Sam, is your side done?

Actions #8

Updated by Greg Sutcliffe about 11 years ago

  • Status changed from Need more information to Closed

Closing this, the compute rename was a while back.

Actions #9

Updated by Greg Sutcliffe about 11 years ago

  • Status changed from Closed to Assigned
  • Assignee changed from Greg Sutcliffe to Sam Kottler
  • Target version set to 1.2

Re-opening, apparently the rpms haven't been renamed yet.

Actions #10

Updated by Dominic Cleal about 11 years ago

  • Assignee changed from Sam Kottler to Dominic Cleal
Actions #11

Updated by Sam Kottler about 11 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100

Applied in changeset commit:"700122c429c5d399f676b6ffdc3414ba694ea2e1".

Actions

Also available in: Atom PDF