On Tue, Jan 12, 2010 at 3:21 PM, inode0 <[email protected]> wrote: > On Tue, Jan 12, 2010 at 2:27 PM, Stephen John Smoogen <[email protected]> > wrote: >> "EPEL is purely a complimentary add-on repository and does not replace >> packages in RHEL or layered products." >> >> to >> >> "EPEL is purely a complimentary add-on repository and does not replace >> packages in RHEL. [Package conflicts are determined by what is openly >> available from Red Hat's tree (currently located at >> ftp://ftp.redhat.com/pub/redhat/linux/enterprise/) ] > > I would appreciate you putting up with one more serious question from > the perspective of a user. Since RHEIPA, RHSAT, RHDirServ, RHCERT, > RHWAS, and more fall into this new category and since the upstream > versions of many of those have been suggested as desirable targets for > inclusion in EPEL can you help me understand what a package conflict > means in this case? Is it a conflict at the package level? Is it a > conflict at the file level?
I am not sure what you mean fall into this new category. None of the channels listed above seem to be in ftp://ftp.redhat.com/pub/redhat/linux/enterprise/ [Nor are some of them on ftp://ftp.redhat.com/ in a form that could be used to build file/package conflicts from.] Could you define it a bit better for me? -- Stephen J Smoogen. Ah, but a man's reach should exceed his grasp. Or what's a heaven for? -- Robert Browning _______________________________________________ epel-devel-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/epel-devel-list
