Re: [Warzone-dev] Splitting the repository into source data sections?
Am Dienstag, 23. September 2008 06:08:37 schrieb bugs buggy: I was thinking it might be a good time to either split the repository into dedicated sections, or have multiple repositories. Can someone state the pros and cons for that? (esp. the pros...) What led to that idea? One should be only used for source, and the other only for data. The question remains, do we stick with GNA, even though they still are having some issue? What issues do they have? I was told by non-Gna-members that the SVN server had been replaced? (Sadly my communications with the project itself can somehow not be established... :( ) Is having multiple repositories allowed on GNA? I would have to investigate whether multiple repositories for one project are possible via Savana. But having multiple projects for one thing on Gna is afaik not an issue (this is not an official statement, will have to ask for that, too :P ). I am building this view on the statement Large software distributions are not allowed; they should be split into separate projects. as found on https://gna.org/register/. Should we take the data to a new host to test the waters? Or is having data not allowed as a 'project' on like source forge, or whatever? I do not know the SourceForge rules and I do not know anyone of their staff. Furthermore SF is not free, they have loads of ads, even more flash and their servers are not really faster either... So if we find anything else, I'd rather go with that instead of SF... To bring this up again: Why exactly can we not host our repository on wz2100.net? That sounds like the most effective and simple solution to me... (In case we move away from Gna for whatever reason...) We'd lack the project management functions as found in Savana, but then we are not that many people and adding a new SVN access every few months doesn't sound too bothersome. Permission to do that can even be handed out to other project members, so our admin (*waves to Kamaze*) does not have to be bothered with it. --Devu signature.asc Description: This is a digitally signed message part. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Splitting the repository into source data sections?
Am Dienstag, 23. September 2008 12:00:18 schrieb Freddie Witherden: Hi Dennis, Hello Fred and the rest of the Warzone 2100 Resurrection Project! On 23 Sep 2008, at 08:28, Dennis Schridde wrote: Am Dienstag, 23. September 2008 06:08:37 schrieb bugs buggy: I was thinking it might be a good time to either split the repository into dedicated sections, or have multiple repositories. Can someone state the pros and cons for that? (esp. the pros...) What led to that idea? Easier for distributors/packagers (separate packages). We are not all forced to re-download ~20MiB of images when someone decides to re- compress the tiles/textures. One idea I just got: We had that issue with originals and works-in-game data. Maybe use different repositories for those? data, data-for-game, game? The data-for-game repos could be autogenerated from the data repository regularly. (Cronjob, buildbot, ...) So data-creators would work on the originals in the data repository, and would not have to care about converting every piece themselves. We also would not require everyone to regenerate the for-game data themselves, since they can use the data-for-game repos if they want. That repos would also be what we finaly create the releases from. One should be only used for source, and the other only for data. The question remains, do we stick with GNA, even though they still are having some issue? What issues do they have? I was told by non-Gna-members that the SVN server had been replaced? (Sadly my communications with the project itself can somehow not be established... :( ) It works fine for me. Is having multiple repositories allowed on GNA? I would have to investigate whether multiple repositories for one project are possible via Savana. But having multiple projects for one thing on Gna is afaik not an issue (this is not an official statement, will have to ask for that, too :P ). I am building this view on the statement Large software distributions are not allowed; they should be split into separate projects. as found on https://gna.org/register/. Thanks, would really appreciate it if you could. I am currently trying to somehow connect with the rest of the team, but it seems the mailinglists are all moderated (or malfunctioning) so it might take a few days... To bring this up again: Why exactly can we not host our repository on wz2100.net? That sounds like the most effective and simple solution to me... (In case we move away from Gna for whatever reason...) We'd lack the project management functions as found in Savana, but then we are not that many people and adding a new SVN access every few months doesn't sound too bothersome. Permission to do that can even be handed out to other project members, so our admin (*waves to Kamaze*) does not have to be bothered with it. What if Kamaze gets hit by a bus? Shared root access? Or goes nuts and rm -rf's everything? I know already 3 mirrors of the SVN tree (Giel, me, Launchpad). I also mirror the download area on Gna (to prevent issues like the rm-rf-hack which hit us last time). We can do the same for the website and databases, I think. Something I forgot? Greetings, Devurandom signature.asc Description: This is a digitally signed message part. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Splitting the repository into source data sections?
Hello WZRP, hello Per! Am Dienstag, 23. September 2008 13:05:58 schrieb Per Inge Mathisen: One idea: How about using just one repository, but shaped like this: trunk/ branches/ tags/ then a next level (example from inside trunk): trunk/code/ trunk/data/ trunk/originals/ so if you wanted to download the latest of all, you would do svn up on trunk, while if you wanted to just grab a new code branch, you'd do svn up on trunk/code only. Sound good, too. I do not see what you gain from using separate repositories, instead of separate directories inside a single repository. Am I missing something? I think it is a feature that with a single repository we would still have one global revision ID for everything, so you could say, test revision NNN, instead of test code revision NNN with data revision MMM. data/trunk data/branches/X ... Would work too, and is equivalent to the split-repos approach. (Unless SVN shows bad performance with lots of data/revisions in one repos.) (Sidenote: For Git (git-svn) this would mean to mirror the data/originals/code into different repositories, but that should not be an issue, I think.) --Devu signature.asc Description: This is a digitally signed message part. ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
Re: [Warzone-dev] Splitting the repository into source data sections?
Am Dienstag, den 23.09.2008, 14:51 +0200 schrieb Dennis Schridde: Hello WZRP, hello Per! Am Dienstag, 23. September 2008 13:05:58 schrieb Per Inge Mathisen: One idea: How about using just one repository, but shaped like this: trunk/ branches/ tags/ then a next level (example from inside trunk): trunk/code/ trunk/data/ trunk/originals/ so if you wanted to download the latest of all, you would do svn up on trunk, while if you wanted to just grab a new code branch, you'd do svn up on trunk/code only. Sound good, too. Hi all i like per's idea (in an artist's point of view) trunk/data trunk/code originals/ ... looks somehow better than trunk/ trunk/data/ originals/ ... and imo better than code/trunk code/branches code/tags data/trunk data/branches data/tags originals/ and you simply can checkout trunk/ and have everything you need, if you only want to update source, go in code and update it.. i'm not for seperate repositories, code works with data and it should be consistent each revision. The data-for-game repos could be autogenerated from the data repository regularly. (Cronjob, buildbot, ...) So data-creators would work on the originals in the data repository, and would not have to care about converting every piece themselves. i would like to keep originals for work-in-progress, unfinished things, models don't have to be updated very often. with the (future) pie converter it isn't that difficult to do it every time regards elio ___ Warzone-dev mailing list Warzone-dev@gna.org https://mail.gna.org/listinfo/warzone-dev
