On Fri, Sep 2, 2011 at 4:06 PM, Thomas Perl <th.p...@gmail.com> wrote: > Hi, > > 2011/9/2 anatoly techtonik <techto...@gmail.com>: >> I've used http://gitorious.org/+pyside-developers/pyside/buildscripts >> to get latest PySide on Fedora 15. But, unfortunately, it appeared >> that compiled version is not the latest. >> [...] >> It doesn't seem that these repositories are outdated, so why git >> fetched these outdated versions? >> It looks like buildscripts should be updated every time for new >> release, but I couldn't find where git stores info about revisions in >> submodules to switch to version 1.0.6. Any help? > > It's here: https://github.com/PySide/BuildScripts > > I don't yet have write access to this repository, so I was not able to > push the repository URL changes (PySide now uses Github) and newer > revisions to this. > > As for updating to the latest version - Git sub-modules by default > don't "track" a specific branch, but rather point to a specific > revision in time (that's actually good if you want to depend on > getting the known-to-be-working revision of code and not get any > breakages with future updates, but it's bad if you really want to > track the updates). The README file in the buildscripts states how to > do this (update every submodule to the current master branch HEAD): > > git submodule foreach git checkout master > git submodule foreach git pull > > I'll try to get the fixes in the BuildScripts repository on Github > once I've got write access to the repository. > > HTH.
Thanks for the explanation. If PySide now uses Github, it would be nice to place links to it in Gitorious repository descriptions. -- anatoly t. _______________________________________________ PySide mailing list PySide@lists.pyside.org http://lists.pyside.org/listinfo/pyside
