Am Wed, 25 Jun 2014 14:44:17 +0000 schrieb Brett Smith <[email protected]>:
> Good list... > > We need to do a few infra structure things first > > I. Get the new build nodes running and working > II. do a source by source promote from the staging label to the > release label III. automate the lftp mirror of fedora 20 (needs to be > reusable code for CentOS 7 and f21) IV. Get mirrorball running in > current mode ever few hours V. Run a group build after each run of > mirrorball > > 1) I have a complete group-os built on the current staging label so > I know the plain group recipe works (not from comps.xml) > > 2) see above IV and V > > 3) Building from comps.xml has proven more challenging than I wanted. > However the code that matches the rpms in comps.xml to the conary > equivalent is solid and we can use it to figure out a solution that > works. > > 4) Yep. > > 5) Replacing Fedora artwork is going to be a HUGE undertaking with > encapsulation. We basically pass the unmolested rpms off to rpm to > install. Changing the artwork at import or install time would be a > nightmare. The idea was to put replacement packages of the parts that contain artwork (at least the most obvious ones) on a fl:3 label and replace the original packages in our custom foresight groups with these. That will probably a bit of work before we identified all of them. I wonder if we could just rebuild the rpms with tweaked content or if we build conary packages but providing an empty :rpm component with the nessesary dependancies. > 6) That works for the most part. I was able to adopt a base fedora > system with conary. Hilarious as it seems conary in a tar ball and > some configs would allow you to posses a Fedora install. We possibly > need to get a brownfield solution going. <ducks> Whatever a brownfield solution is. Going to ask "the internet" > > 7) Yep. > > > > > -- > > Brett C. Smith > [email protected] > Sr Software Developer > Platform Deployment Technologies > (919)531-6635 -- x16635 > > ________________________________________ > From: Foresight-devel > <[email protected]> on behalf of Mark > Trompell <[email protected]> Sent: Tuesday, June 24, 2014 6:31 > AM To: [email protected] Subject: > [Foresight-devel] Next stepts toward fl:3? > > Heya, what are the next steps we need to take to get a working fl:3. > What I see is: > 1) We need a complete group of the fedora import. > 2) we need a complete update to that import and keep rgular updates > going (including regular group rebuilds) > 3) We need to build sane groups on the fl3 label that somewhat reflect > what our f3 looks like > 4) We need to get some extra repos imported (rpmfusion et al) > 5) We need the artwork of fedora replaced with sane one (foresight > artwork) 6) We need to provide a way to convert fedora 20 to fl:3 > 7) We need to provide a way to do a native fl:3 install > > Anything I've forgotten here? > So let's get into the details. > Brett, Micahel, any input here especially on 1) 2) and 4) > > > > -- > Mark Trompell > > Foresight Linux Xfce Edition > Cause your desktop should be freaking cool > (and Xfce) > _______________________________________________ > Foresight-devel mailing list > [email protected] > https://lists.foresightlinux.org/mailman/listinfo/foresight-devel > _______________________________________________ > Foresight-devel mailing list > [email protected] > https://lists.foresightlinux.org/mailman/listinfo/foresight-devel _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
