On Fri, Aug 27, 2010 at 13:47, Kevin Fenzi <kevin(a)scrye.com> wrote:
On Wed, 25 Aug 2010 19:15:48 +0100
Paul Howarth <paul(a)city-fan.org> wrote:
> Is there any forecast for if/when this is going to happen? I have a
> bug waiting on this:
> I was intending to clone a package from the workstation optional
> packages in EPEL but need to see if they are going to be included in
> the buildroots instead.
Yeah, currently my understanding of where we are at:
- Dennis is asking RHEL folks if there is now, or is going to be a
"Productivity" channel for RHEL6 server. If there is, we can use this
as we do in EPEL5 buildroots. That way everything works and everyone
can install things fine.
- If there isn't going to be such a channel, we are in a bit of a mess.
We can do:
a) Just say EPEL is sever only. Sorry workstation people. ;(
b) We can try and use both server/workstation to build against.
However, this means that some packages will require BOTH channels, and
if you have a workstation you can't install something that needs a
package from server and vice versa.
c) Do what you were suggesting and import only those workstation
packages we need to build/use our EPEL packages. However, this means we
are shipping a RHEL workstation rpm to server people, which might get
RHEL folks mad and want them to get a Workstation entitlement, etc.
d) Scrap everything when centos6 comes out and build against that. ;)
e) Your clever idea here.
So, we are mostly waiting right now to hear about the questions about
productivity. Sorry it's been a pain.
I don't know but I seem to be feeling a great amount of DEJA VU from RHEL-5..
Stephen J Smoogen.
“The core skill of innovators is error recovery, not failure avoidance.”
Randy Nelson, President of Pixar University.
"We have a strategic plan. It's called doing things.""
— Herb Kelleher, founder Southwest Airlines