Koji "hidden" packages proposal

[Dennis Gilmore]

On Saturday 15 March 2008, Mike Bonnet wrote:
> On Fri, 2008-03-14 at 19:55 -0500, Dennis Gilmore wrote:
> > On Friday 14 March 2008, Mike Bonnet wrote:
> > > I've written up a brief proposal about how "hidden" packages may be
> > > supported in Koji.  The objective of this is to enable building EPEL
> > > packages in Koji.  I wrote this up fairly quickly, and I'm sure I
> > > haven't thought through all the issues, but I wanted to get the ball
> > > rolling.  Let me know if you have any questions/comments/ideas/issues
> > > relating to this proposal.
> > >
> > > http://people.redhat.com/mikeb/koji/koji-hidden-packages-proposal.html
> > >
> > > Thanks,
> > > Mike
> >
> > the tree will have to be nothing like /mnt/koji/packages
> >
> > instead it will have to be like
> > http://download.fedora.redhat.com/pub/fedora/linux/  so that you can use
> > rsync  and repo mirroring tools to sync the content and keep trees in
> > sync. ill leave it up to Seth to explain more but hit micro repository
> > option he is working on would allow us to pull the existing repodata
> > intothe new repodata.
>
> I'm not really sure what you're talking about.  *No one* will be
> mirroring the hidden packages in the case we're talking about (building
> EPEL in Koji), these will be RHEL binaries, and only available to the
> builders.
What im talking about was the proposal put forward  when we had the buildsys 
meeting  the proposal that  we all said sounded like the way to move forward.  
This is not that proposal.   importing packages is the one thing that hurts 
koji from getting wider use outside of fedora.  Some people will import the 
data.  Most do not want to.  Fedora will be mirroring RHEL content from RHN,   
people outside of fedora will be mirroring fedora and building on top of 
that.   

> > We really only need to have a command that can suck the repodata into the
> > database.  so we know about the packages.
>
> We have a command that can suck data about packages in to the database.
> It's "koji import".  The proposal is designed to work within the
> framework of that we already have in Koji, to try to minimize the number
> of changes and thus the time it'll take to implement.


sure koji import --repodata  --url=<http|ftp|file>://<host>/path/to/repodata

> The micro repository option Seth has talked about sounds interesting,
> but it doesn't really help with the issue of making packages available
> to Koji builders without making them available to the world.
sure it does,  we have an internal only tree  thats on the phx internal 
network and not available outside of phx,   just as we do now. 

Dennis
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.fedoraproject.org/pipermail/buildsys/attachments/20080315/b8e7b05c/attachment.bin