On Thu, 19 Nov 2009 14:40:18 +0100 Jan Pazdziora <[email protected]> wrote:
> On Thu, Nov 19, 2009 at 02:13:08PM +0100, Jan Blazek wrote: > > > > I have an idea how to do this. If we don't want to split koji tags > > (which I think would be an overhead) we need to specify somewhere > > the lists of packages which would go to which repository. I'd > > prefer to use comps files as these lists. We take a similar > > approach for Satellite where there are two separate comps files for > > Satellite and EmbededDB. > > > > Next step would be to force mash to take into account only those > > packages specified in comps. This would need to patch mash to add > > this feature. > > > > How do you like this idea? > > While it would certainly be interesting to have this feature, patching > the mash, getting it upstream, etc. seems like bringing unnecessary > delay. Can you use the same mash config which is used now for the > Spacewalk server repo, have that setup, and only then start working on > patching mash to support comps, and once we get the new mash in EPEL > or whatever is running on koji.rhndev.redhat.com, convert the current > config to comps? > > I definitely prefer having the yum repo available today without comps > over having it in two weeks with comps. > > Thank you, > OK. I'll work on a workaround for now and then take a look on patching mash. -- Jan Blazek <[email protected]> Release Engineering, Red Hat _______________________________________________ Spacewalk-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-devel
