[PySide] BuildScripts and archived repositories on GitHub

[Thomas Perl]

Hi,

2012/3/21 Matti Airas <matti.p.airas at nokia.com>:
> On 21.03.2012 11:38, ext Thomas Perl wrote:
>> Yes, I'd also like to have the old repositories available somehow. I
>> have a checkout from some weeks ago, so if nothing else comes up, I
>> could upload that somewhere (maybe something like
>> github.com/pyside-old-repositories-2012-03/[...] to make it clear that
>> these are the repositories that are considered "old" as of 2012-03).
>>
>> It would be great if someone from the PySide Core Team could upload
>> these repos, though, because I'm not sure I have the latest revisions
>> from all the old repositories (or just tell me the revision numbers
>> and I'll check if I have the latest).
>
> I don't really see any reason to delete the apiextractor and
> generatorrunner repositories from Gerrit. In my opinion, they can well
> reside there, and together with the Gitorious mirrors provide all the
> archiving functionality you need. It's not really constructive to keep
> muddling the project layout with unofficial GitHub repos because new
> commits have to land in Gerrit to fulfill the contribution agreement
> requirements. Hence, I'd also prefer if the build scripts would point to
> the official repos - but that's of course up to you.

I'll definitely update the build scripts to use the new repositories
and the new structure and go forward with the new, simplified build
structure for PySide.

However, for some use cases in the next few months, it might still be
useful to be able to access the old pre-Qt Project repositories (with
the "offending" commits still included). One example might be to build
PySide Mobility (it seems like it is broken with the new structure,
have to investigate) until we get it fixed or to "replay" the PySide
on Android instructions with the old repos in case there are problems
with the new repository layout and the instructions. It might be
useful in debugging and finding errors (maybe there are regressions
from migrating apiextractor and generatorrunner into shiboken, not
that I would expect any). Of course, the old repos should be clearly
marked as such, and no new development should happen there. Disk space
is cheap/free, and keeping the original repositories around for a few
more months might prove to be useful, and should not hurt (if they are
clearly marked as old, deprecated and usually dangerous - both in the
URL and maybe with a "OLD-REPOSITORY-DO-NOT-USE.txt" file committed to
it containing a description where to get the latest version).

Thanks,
Thomas