) it's becoming a nightmare more than a solution and at this point I feel like almost every try to get used to proposed workflows and its concept is in over my head (Git's Submodules & Superprojects, Hg's Subrepositories, Symlink based dependencies...) cause I don't think I'm reaching any satisfactory conclusion... I started trying to learn the basics about how Git (and, more recently, Mercurial (Hg)) works, but as soon as I try to think the way to manage shared files from different locations (like the ones intended to be stored in the "utilities" folder) between repositories in order to establish a consistent way of work, or simply try to adapt the repositories file structure system (which basically requires to have every involved file inside a single folder or "working directory") to the way AS folders structure imposes on how files must to be located, well... lets say everything start becoming (even) more and more complicated than it already is, and I think I start to feel the temptation to stop researching about all this and simply get back to my old (and horrible, BTW) way of work, which basically consisted of go making simple copies or backup of files with a little description about changes in their name from time to time. But of course I've never felt happy with this primitive way of work and I still want to move to another more beneficial solution, which at least provide some kind of reliable Version History and source code backup control, so although I how this is like a very "generic" issue beyond AS scripting field, I've finally decided to ask for advice here just in case someone has gone through a similar situation before and has something to say to the respect, or... about other possible alternatives or simpler workarounds or whatever, taking into account any AS scripting project will ever be so complex than what any Git/Mercurial kind of solutions are designed to manage, I mean, maybe I'm simply over-complicating things for what I really need, and I simply can't see the forest for the trees... After all, and as I said, I don't really need anything beyond Version History and appropriate code backup system, I mean, I can't even think on social coding and stuff like that for now, but I'd really like to start doing things *rightly* once and for all, and something tells me this matter could be like a very good starting point for it.
Hmmm, I hope I've been able to express myself around the issue at least but, summarizing, my main problems/concerns for what I've seen until now, are related to how shared files can be tracked by different projects (for example, files like: rl_utilities.lua) in order to avoid history messes/conflicts and the necessity of maintain them separately, plus... folders structure limitations (like how to correctly manage files outer the main repository folder). Well, greetings and thanks in advance for any help/correction/advice!
). But, if I understand it well, you are proposing something like a "super-project", or rather: "SUPER-REPOSITORY", which should contain ANY other project as long as any shared file between them exists, isn't? (otherwise, files interaction between totally independent repositories wouldn't be possible in Git or Mercurial as far as I know). Well, certainly that possibility have passed through my mind at some point but the lack of sureness around all this, made me start experimenting with independent "per project/tool" repositories , but this is something about I definitely want to delve and requires much more thinking for my part, as I like to start on the right foot if possible, cause I'm always afraid about if once initiated the workflow of choice, there will be a point of "no return" for deep changes in the way it was conceived.
) post I deduce that you want to work with different versions of AS and so, is that right?