Just started using mock to rebuild some srpms. I have two I want to rebuild, problem is the first creates a dep that is required by the second. Is there an automated way to populate an additional repo/cache that mock would look at when building the second so I could queue both? Although I haven't tried, I presume I could drop the output from the first build into a dir, createrepo it and add that into the config file then build the next package but that's not very slick :) Thanks! jlc
On Sat, 2009-04-11 at 13:55 -0600, Joseph L. Casale wrote:> Just started using mock to rebuild some srpms. I have two I want to > rebuild, problem is the first creates a dep that is required by the second. > > Is there an automated way to populate an additional repo/cache that mock > would look at when building the second so I could queue both? > > Although I haven't tried, I presume I could drop the output from the first > build into a dir, createrepo it and add that into the config file then build > the next package but that's not very slick :)koji can do this, but koji is not a small solution. -- Ignacio Vazquez-Abrams <ivazqueznet at gmail.com> PLEASE don't CC me; I'm already subscribed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part URL: <http://lists.centos.org/pipermail/centos/attachments/20090411/b2bdb418/attachment-0002.sig>
Joseph L. Casale wrote:> Just started using mock to rebuild some srpms. I have two I want to > rebuild, problem is the first creates a dep that is required by the second. > > Is there an automated way to populate an additional repo/cache that mock > would look at when building the second so I could queue both? > > Although I haven't tried, I presume I could drop the output from the first > build into a dir, createrepo it and add that into the config file then build > the next package but that's not very slick :) > > Thanks!That's what I do. It is slick. I've got a shell script that takes a list of packages. The script defines a destination directory. Before it builds a package, it removes any repo stuff in that directory and runs createrepo on it. The destination directory is part of the mock configuration file. It then builds the package and upon success moves the results to the destination directory. Works extremely well for me.