On Wed, Mar 19, 2014 at 01:09:41AM +0100, Martin Bähr wrote: > Excerpts from Michael K. Johnson's message of 2014-03-18 11:40:57 +0100: > > Just to be clear, there are definitely people in the Fedora community > > who know what we are doing. > > are there people discussing what we are doing?
No idea. > > I'm afraid that this is where I fall down. I'm not sure I'll be > > much help. > > uhm, on the contrary it appears. what you wrote is almost as good as an > abstract in itself :-) > > [ text snipped ] > > i'd just like to copy-paste this text as a whole into the submission form :-) Heh. Well, don't paste anything you aren't comfortable speaking to. > > * Using Conary's extensive package build automation to make it easier > > to build better packages for Fedora. > > can you elaborate how we would do that? > a recipe that depends on and invokes rpm build tools and spits out an > encapsulated rpm instead of a native conary package? Essentially, yes. Basically, taking advantage of Conary's superclasses, rich policy, automatic componentization, etc, and making it available to Fedora packagers so that they have less work to do to make high quality packages, and can concentrate only on the useful packaging. Most of what you're used to with writing recipes for Foresight... > well, i suppose it would be a factory that can handle all rpm packages > otherwise a packager would have two, the conary recipe and the rpm spec to > manage for each package. What I had in mind here would not require a spec file to be maintained. Conary would probably write a minimal one to call rpmbuild but control the build process. There is more than one way to do that, and if there is interest on the Fedora side we can discuss which way works best then... This is something that Andy Grimm did a lightning talk on at a previous fudcon, to some interest. > the summary is just the kind of outline i was looking for. > i found nothing that i could add or remove from it or from the text. > i'd present the talk as made by the foresight development team with me just > acting as a speaker. In that case, though, I suggest you develop it further on the list here, so that everyone can contribute. _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
