[Fedora-packaging] Packaging guidelines for Emacsen add-on packages

seth vidal skvidal at linux.duke.edu
Wed May 30 21:25:29 UTC 2007

On Wed, 2007-05-30 at 23:27 +0300, Ville Skyttä wrote:
> On Wednesday 30 May 2007, Jesse Keating wrote:
> > On Wednesday 30 May 2007 15:47:21 Ville Skyttä wrote:
> > > If I understand correctly, this is an orthogonal issue which isn't
> > > limited to querying rpm.  For example, different *emacs versions inside
> > > and outside the buildroot is just as likely as different rpm versions.
> > >  What makes querying them for versions instead of rpm safer, more
> > > predictable, and more reproducible?
> >
> > Because you're querying the emacs in the chroot not outside the chroot.  In
> > the case of rpm, the rpm _outside_ the chroot was used to populate the
> > chroot, and the rpm database version that winds up in said chroot does not
> > match the version of rpm that gets installed inside the chroot.
> mock runs rpmbuild inside the chroot.  Why doesn't it break?  --nodeps?

all the operations performed on the rpmdb in the chroot are done from
outside the chroot, not inside. 


More information about the Fedora-packaging mailing list