2010/7/16 An Yang <[email protected]>: > 在 2010-07-16五的 11:10 +0200，Francisco Javier Cuadrado写道： > > 2010/7/16 An Yang <[email protected]>: >> 在 2010-07-16五的 10:33 +0200，Francisco Javier Cuadrado写道： >> >> 2010/7/16 An Yang <[email protected]>: >>> Hi, >>> >>> 在 2010-07-15四的 15:56 +0200，Francisco Javier Cuadrado写道： >>> >>>> Also there was an idea that I did not give it a chance until this >>>> desperate moment : use mock to create a MeeGo chroot (using MeeGo >>>> repository) and from there build all source packages from MeeGo, but I >>>> don't know if this will work and if mock can automate building >>>> process. >>> >>> This method should work. >>> if you have experience with rebuilding Fedora, then you should know how >>> to >>> rebuild Meego. >>> if not, my suggestion is rebuild Fedora12 with your own repo first, and >>> you >>> should know the method. >>> >> >> I haven't any experience with rebuilding Fedora or another distro, I >> used mock to compile some packages but nothing important. So, please, >> can you explain me more details about that? >> >> you should create a mock config file for meego in /etc/mock/, for example >> meego-1-i386.cfg. >> the content you can find in /etc/mock/fedora-12-i386.cfg, replace fedora >> with meego. >> >> and than you could use >> mock -r meego-1-i386 rebuild xxx.src.rpm >> to rebuild it. >> > > Ok, that was my initial idea. But how can I automate compilation of > all packages? > > rebuild all packages I think it's waste time, all packages without meego's > logo and trademark are free, you could just use them. > if you just want to rebuild some packages, and if you do not break the deps, > you could rebuild them from a to z. >
Then, if I rebuild a modified package and I want to create a MeeGo image that uses it, how can I include this package? Will I have to create a repository with my modified packages and use mic2 with that repository and MeeGo repository? > >>> If you got any problem, feel free to feedback-:), >>> Intel guys use some tricks in their OSB, you should do it again in mock. >>> >>> >> >> My idea, that I said yesterday, is to have an automated system that >> use a mirror of source packages from MeeGo, and it compiles them, >> although source packages of this mirror will be modified before, so I >> can get a repository of binary packages that I can use to create a >> MeeGo image. >> >>> >>> good luck. >> >> --- >> Regards, >> Fran >> _______________________________________________ >> MeeGo-dev mailing list >> [email protected] >> http://lists.meego.com/listinfo/meego-dev >> >> >> _______________________________________________ >> MeeGo-dev mailing list >> [email protected] >> http://lists.meego.com/listinfo/meego-dev >> >> > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > > > _______________________________________________ > MeeGo-dev mailing list > [email protected] > http://lists.meego.com/listinfo/meego-dev > > _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
