Hi Daniel,
to ensure we keep track (and limit) of what non-Fedora rpms make it to
the builds, should the rpm collection step... ?
- only grab rpms that say .olpc
- complain about rpms that don't...
This would mean that in the package listing, it's non-ambiguous what
packages we're carrying.
On 02/28/2011 02:37 PM, Martin Langhoff wrote:
Hi Daniel,
to ensure we keep track (and limit) of what non-Fedora rpms make it to
the builds, should the rpm collection step... ?
- only grab rpms that say .olpc
- complain about rpms that don't...
This would mean that in the package
On Mon, Feb 28, 2011 at 2:44 PM, Simon Schampijer si...@schampijer.de wrote:
What would be the preferred place to put 'olpc' in the rpm name? Between
the distribution version and the 'arch'? Like:
Version: 0.92.0
Release: 1%{?dist}.olpc
Yes - dsd links to
FWIW, the original intent was *only* to allow SRPMS in the dropbox; we were
going to explicitly rebuild the RPMs from the SRPMS in mock and use only the
built RPMs. In addition to ensuring compliance with licensing provisions,
this was also intended as a developer aid: at the time, it was often
