On Wed, Mar 19, 2014 at 03:43:17AM +0100, Martin Bähr wrote: > well, this topic opens a lot of questions that we won't get answers to in the > next two months i think, since we'll still be busy with the base. we may get > those answers once we come to creating additional packages as it could be > interesting just for us to not only build foresight packages, but rpms that we > can submit to fedora. (and here i believe the specfile must be complete so > that > the rpm can be rebuilt without conary tools. not sure if a generated spec can > do that, unless conary can generate the spec from a recipe. now that would be > interesting!)
Enticing but not really feasible as it stands, because we could not integrate conary policy directly into a spec file. There are really two possibilities: 1. rpmbuild adds functionality to invoke cvc and converts the resulting build output to a standalone RPM. While this might make simple packages simpler, it could make complex packages harder so it would be used in practice only for simple packages that aren't that hard to maintain anyway, making it hardly worth the investment. And in this mode, it is hard for me to figure out how to use superclasses effectively. And it doesn't help at all with maintaining file lists. 2. conary controls the build process, creating a spec file that hands control during the build process back to conary, via some communication method yet to be determined; for example, at the end of %build, it could invoke a process that would communicate back to the driving conary process that now it should run all destdir policy. These possibilities would share almost no code, so one doesn't help us get to the other. The first possibility is the only one that creates a standalone RPM and it's a lot of work for little or no reward. The second possibility could make RPM packaging a lot easier, but does not create a standalone RPM. > > This is something that Andy Grimm did a lightning talk on at a > > previous fudcon, to some interest. > > can you help me track that down? Andy told me about it afterward. I don't know that there's anything to track down about it... _______________________________________________ Foresight-devel mailing list [email protected] https://lists.foresightlinux.org/mailman/listinfo/foresight-devel
