On 03/06/14 22:34, Tristam MacDonald wrote:
That's all well and fine philosophically, but what about from the
user's perspective?
Right now they can clone the git repository, and immediately load
textures (albeit from a limited set of formats). If we switch to an
external dependency, then we are still maintaining forked code, and
now the user has to go clone *two* git repositories.
I'm not seeing the current system as so onerous that it is worth
inflicting extra pain on the users.
- Tristam
As far as I can tell the subrepos would be cloned along with the main
repo. Although it seems subrepositories are not recommended.
I think we should try to get on a tighter release schedule after 1.2 is
released as users probably shouldn't be using the development code
anyway. We can package the dependency but should it be developed in the
pyglet tree?
Adam.
--
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/pyglet-users.
For more options, visit https://groups.google.com/d/optout.
