Bug#644943: Please switch source package to OCE
bouzim at gmail.com
Wed Nov 2 13:58:53 UTC 2011
On 2011/11/1 D. Barbier wrote:
> On 2011/11/1 Adam C Powell IV wrote:
>> That's a good question. I could go either way:
>> 1. tart a brand new repository, since it's a new package with new
>> names -- but then start with a new changelog; or
>> 2. Use the oce tarball as a new "upstream" on a renamed or cloned
>> repository, or a branch, to more clearly show the changes
>> between OCC and OCE.
>> I think #1 makes more sense, particularly because it's perfectly easy
>> for someone to "diff -ur" the two trees and see the changes, and we
>> aren't trying to track patch-by-patch changes -- that's OCE upstream's
>> job. We can leave opencascade.git in place, and start a new oce.git in
>> the same place.
> Great, I also prefer #1. Can you please request its creation? (I can
> also do it if you prefer)
> Are there some guidelines about the preferred git workflow when
> upstream has a git repository?
I just found
Adam, can you please run the commands given in the 2nd link in order
to create oce.git repository on Alioth?
More information about the debian-science-maintainers