2009/2/4 Julian Edwards <email address hidden>:
> Consider the case where we have package foo 1.0 and foo 1.1.
>
> Foo 1.1 supersedes foo 1.0. Currently, the only way to keep foo 1.0
> published in a repo is to copy it to another PPA. This means creating
> (if not already done) a new team/person for that PPA.
When you say "the only way", do you mean "the only way within the
current Soyuz code", or "the only way that works in Debian archives at
all"?
The first may be true but I don't think the second is. Manually
maintained archives are perfectly happy holding multiple versions of a
package and this is IME pretty common for archives maintained by
upstream developers. We always had this for baz and bzr before moving
to PPAs.
2009/2/4 Julian Edwards <email address hidden>:
> Consider the case where we have package foo 1.0 and foo 1.1.
>
> Foo 1.1 supersedes foo 1.0. Currently, the only way to keep foo 1.0
> published in a repo is to copy it to another PPA. This means creating
> (if not already done) a new team/person for that PPA.
When you say "the only way", do you mean "the only way within the
current Soyuz code", or "the only way that works in Debian archives at
all"?
The first may be true but I don't think the second is. Manually
maintained archives are perfectly happy holding multiple versions of a
package and this is IME pretty common for archives maintained by
upstream developers. We always had this for baz and bzr before moving
to PPAs.
-- launchpad. net/~mbp/>
Martin <http://