dracut --reproducible by default

Hi,

We are currently considering to feed Dracut with --reproducible in the rpm-ostree[1] project when creating a new OStree[2] tree image. In this way there won't be need to store an additional file when the new initrd file matches an older one. Everything works very well (except the additional step of providing a patched GNU cpio for now).

Reproducible images seem to make a lot of sense, also for users that don't know about the --reproducible option. Is there any reason why this is not done by default?

Thanks,
Giuseppe

1) https://github.com/projectatomic/rpm-ostree
2) https://github.com/GNOME/ostree/

ping?

Quoted 17 lines · Giuseppe Scrivano

Hi,

We are currently considering to feed Dracut with --reproducible in the rpm-ostree[1] project when creating a new OStree[2] tree image. In this way there won't be need to store an additional file when the new initrd file matches an older one. Everything works very well (except the additional step of providing a patched GNU cpio for now).

Reproducible images seem to make a lot of sense, also for users that don't know about the --reproducible option. Is there any reason why this is not done by default?

Thanks,
Giuseppe

1) https://github.com/projectatomic/rpm-ostree
2) https://github.com/GNOME/ostree/

Quoted 16 lines · Giuseppe Scrivano

ping?

Quoted 12 lines · Giuseppe Scrivano

Hi,

We are currently considering to feed Dracut with --reproducible in the rpm-ostree[1] project when creating a new OStree[2] tree image. In this way there won't be need to store an additional file when the new initrd file matches an older one. Everything works very well (except the additional step of providing a patched GNU cpio for now).

Reproducible images seem to make a lot of sense, also for users that don't know about the --reproducible option. Is there any reason why this is not done by default?

Quoted 5 lines

Quoted 5 lines

Thanks,
Giuseppe

1) https://github.com/projectatomic/rpm-ostree
2) https://github.com/GNOME/ostree/

No significant reason, except the penalty of the extra step, which fixes all the timestamps.

Quoted 23 lines · Harald Hoyer

Quoted 21 lines · Giuseppe Scrivano

ping?

Quoted 17 lines · Giuseppe Scrivano

Hi,

We are currently considering to feed Dracut with --reproducible in the rpm-ostree[1] project when creating a new OStree[2] tree image. In this way there won't be need to store an additional file when the new initrd file matches an older one. Everything works very well (except the additional step of providing a patched GNU cpio for now).

Reproducible images seem to make a lot of sense, also for users that don't know about the --reproducible option. Is there any reason why this is not done by default?

Thanks,
Giuseppe

1) https://github.com/projectatomic/rpm-ostree
2) https://github.com/GNOME/ostree/

Quoted 2 lines

No significant reason, except the penalty of the extra step, which fixes all the timestamps.

do you think it makes sense to make --reproducible the default, or do you expect Dracut users, rpm-ostree in this case, to explicitly use it?

Thanks,
Giuseppe

Quoted 6 lines

do you think it makes sense to make --reproducible the default, or do you expect Dracut users, rpm-ostree in this case, to explicitly use it?

Thanks,
Giuseppe

I think, I'll make it the default.