package reprepro
retitle 440872 reprepro: easier way to spread arch:all packages needed
severity 440872 wishlist
thanks
* Cameron Dale <[EMAIL PROTECTED]> [070906 21:14]:
> On 9/5/07, Bernhard R. Link <[EMAIL PROTECTED]> wrote:
> > As reprepro does not realize that there was a new architecture added,
> > it cannot special case that. And even if it could, and there would be
> > multiple other architectures yet, where should it copy them from, and
> > if the versions of their arch:all packages differ, which should it
> > choose?
>
> I certainly understand what you're saying, but I think there is a way
> to do this for the most common case of all arches having the same
> arch:all packages (and versions).
Indeed but there is no way to do it automatically nor should it be done
without explicit request.
I hope the new database handling I'm currently implementing for the
upcoming 2.4.0 will at least allow me to detect the existance of new
architectures and give a better hint in that case.
> Perhaps a new command or option to
> the export command that says "sync all arch:all packages with all
> architectures". It would then find all the arch:all packages available
> in all the architectures, and add them to the archs that are missing
> them.
A new command command so that one does not have to use a pull rule
might indeed be useful. Especially as an automated way to limit what
architectures new arch:all packages are added to when package tracking
is active is on my TODO list, and that will need some special command
to recalculate spreading of arch:all packages anyway, so I guess that
might be easily extended to just equally spread arch:all packages.
Hochachtungsvoll,
Bernhard R. Link
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
