[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Best stab at questions

After working through these questions (which did help the
presentation[1]), I wanted to highlight these conflicting answers as an
example of what is confusing about the packaging process.  The key to
the answer is the phrase "depends on".  Stephen uses it one context and
Tom another.

Here is how I am addressing it:

        Note: add-on packages that are not dependencies can exist
        outside of EPEL, since they are not needed to build the package
        from source or to support package installation, such as system
        libraries. An example of this is an open source game engine and
        a set of game levels that are not free and open content.  The
        game engine can be built and installed by itself without any
        level, for example, so someone can build free and open levels.
        The levels make for a nicer playing experience, but are not
        required, and could be in an external repository.

On Fri, 2008-06-13 at 17:22 -0600, Stephen John Smoogen wrote:

> > 3) If we deploy to EPEL, do all of the packages we depend on need to be in EPEL as well?
> No. You could use packages in your appliance outside of EPEL, but in
> the case of 'conflicts' it could cause problems in integration or
> updates. Areas where I see packages not being in EPEL would be:
> a) Other propietary packages.
>  b) Reliance on packages that do not meet EPEL's packaging structure
> (putting things in /opt. Requiring packages that are 'newer' than RHEL
> "Core" packages etc.

... and ...

On Thu, 2008-06-12 at 11:29 -0400, Tom "spot" Callaway wrote: 
> > 3) If we deploy to EPEL, do all of the packages we depend on need to
> > be in EPEL as well?
> Yes.

Short answers -- all package dependencies must be in EPEL (or RHEL), but
not all things you might "depend on."

- Karsten
[1] I'll post more about this presentation later, but here are the
pieces; the PDF includes notes, which are also found in the 'script'


Karsten Wade, Sr. Developer Community Mgr.
Dev Fu : http://developer.redhatmagazine.com
Fedora : http://quaid.fedorapeople.org
gpg key : AD0E0C41

Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]