* Daniel Baumann dan...@debian.org [090812 21:49]:
when using FakeComponentPrefix, it would be nice if reprepro (at least
optionally) could put the packages for a given prefix into pool/$prefix
just as debian does it.
I think making that possible would be quite complicated. (There might be
Bernhard R. Link wrote:
Is there a reason for storing those file at this place? I only see
disadvantages.
first, debian does it that way and for some people it's important to
replicate the same alike repositories.
second, it's nifty for mirroring. you can rsync over the whole
repository, and
package reprepro
tags 54126 + pending
thanks
* Daniel Baumann dan...@debian.org [090813 16:16]:
Bernhard R. Link wrote:
Is there a reason for storing those file at this place? I only see
disadvantages.
first, debian does it that way and for some people it's important to
replicate the same
Bernhard R. Link wrote:
I think I found a solution: Instead of telling reprepro to put the files
to a different place, one can just change the components to where one
actually wants them. This then only need some code to not have the
prefix than stored in the path of the dists dirs multiple
Package: reprepro
Severity: wishlist
Hi,
when using FakeComponentPrefix, it would be nice if reprepro (at least
optionally) could put the packages for a given prefix into pool/$prefix
just as debian does it.
Regards,
Daniel
--
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562
5 matches
Mail list logo
