Thanks for your help. --update does not appear to be a legal option:

hg clone: invalid arguments
> hg clone [OPTION]... SOURCE [DEST]
> make a copy of an existing repository
> options:
>  -U --noupdate          the clone will include an empty working copy (only 
> a
>                         repository)
>  -u --updaterev REV     revision, tag or branch to check out
>  -r --rev REV [+]       include the specified changeset
>  -b --branch BRANCH [+] clone only the specified branch
>     --pull              use pull protocol to copy metadata
>     --uncompressed      use uncompressed transfer (fast over LAN)
>  -e --ssh CMD           specify ssh command to use
>     --remotecmd CMD     specify hg command to run on the remote side
>     --insecure          do not verify server certificate (ignoring 
> web.cacerts
>                         config)
> [+] marked option can be specified multiple times
> use "hg help clone" to show the full help text


When I simply issue

hg clone --update https://code.google.com/p/pyglet/ 


...does it not fetch the latest and greatest? Keep in mind that I did not 
have a copy of pyglet at all prior to issuing this command, and it 
certainly did fetch *some* version.

Also, just a sanity check, am I correct that someone recently committed a 
change that should be downloadable? I'm referring to this post from the 
15th, 
https://groups.google.com/forum/?fromgroups=#!topic/pyglet-users/JSxcQk_NEDo, 
but when I view the changes listed here, 
http://code.google.com/p/pyglet/source/list, I don't see any updates since 
September.

I appreciate your patience.

Steve
 

On Thursday, October 25, 2012 3:34:22 PM UTC-7, Winston wrote:
>
> Hi Steve- 
>
> Try: 
>         hg clone --update https://code.google.com/p/pyglet/ 
>
> Unlike git, mercurial separates the cloning process (moving data from 
> remote repository to local repository) and the update process (update your 
> working directory with latest files from local repo.) 
>
> -Winston 
>
>
> On Oct 25, 2012, at 2:47 PM, Steve Willis wrote: 
>
> > My apologies. Between posting the message below and being approved for 
> the group (thanks!), I realized Nathan was referring to the revision 
> control version, and not the release version. 
> > 
> > That said, I attempted to get the latest version by doing the following: 
> > 
> > hg clone https://code.google.com/p/pyglet/ 
> > 
> > This version exhibits the problem others were having with this on 
> Mountain Lion before...it runs without error, but no window is visible. 
> Based on the date stamps for the Mercurial download, I think I've still got 
> a version that predates the one Nathan committed recently. This is my first 
> adventure with Mercurial, and I'm sure I'm doing something silly. Any tips 
> on getting a version of the code with the Mountain Lion fix to try out? 
> > 
> > Thanks, 
> > 
> > Steve 
> > 
> > On Thursday, October 25, 2012 9:37:06 AM UTC-7, Steve Willis wrote: 
> > This does not seem to be working for me on system python under Mountain 
> Lion, though this is my first attempt at using pyglet and I might be 
> overlooking something. When I try to run the "Hello, World" example (
> http://www.pyglet.org/doc/programming_guide/hello_world.html), it fails 
> with the following error: 
> > 
> > OSError: 
> dlopen(/System/Library/Frameworks/QuickTime.framework/QuickTime, 6): no 
> suitable image found.  Did find: 
> >         /System/Library/Frameworks/QuickTime.framework/QuickTime: 
> mach-o, but wrong architecture 
> >         /System/Library/Frameworks/QuickTime.framework/QuickTime: 
> mach-o, but wrong architecture 
> > 
> > Any advice would be appreciated. 
> > 
> > Steve 
> > 
> > On Monday, October 22, 2012 8:53:10 AM UTC-7, Nathan wrote: 
> > Just for the benefit of users finding this thread through Google, pyglet 
> now works on system python under Mountain Lion. 
> > 
> > ~ Nathan 
> > 
> > 
> > -- 
> > You received this message because you are subscribed to the Google 
> Groups "pyglet-users" group. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msg/pyglet-users/-/T--DZ1GbnlYJ. 
> > To post to this group, send email to 
> > [email protected]<javascript:>. 
>
> > To unsubscribe from this group, send email to 
> [email protected] <javascript:>. 
> > For more options, visit this group at 
> http://groups.google.com/group/pyglet-users?hl=en. 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"pyglet-users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/pyglet-users/-/8axrr86LmEwJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/pyglet-users?hl=en.

Reply via email to