6.4 overlaps

inode0 inode0 at gmail.com
Mon Mar 18 01:10:04 UTC 2013


On Sun, Mar 17, 2013 at 6:46 PM, Dennis Gilmore <dennis at ausil.us> wrote:
> On dom, 2013-03-17 at 10:55 -0500, inode0 wrote:
>> My lack of understanding the process is pretty limiting. Why in the
>> world does it need to be hardcoded into anything? Surely mash can grab
>> the list from a file or from the environment?!
>
> mash is very simple. it takes the list of packages in the tag and makes
> a repo from them. making sure the rpms are signed by the key defined.
> it has no ability to do anything like has been proposed here.  patches
> are welcome.  but it would require a manually managed list of packages.
> since we don't have that info available.  mash doesn't know about RHEL
> at all.

Generating the list of packages that conflict is easy and there is a
script that does that now. Does mash use createrepo to actually build
the repo? If so I still can't imagine this is very difficult and if I
get some free time I'll look at it.

John




More information about the epel-devel-list mailing list