Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[GiantUrist]

In the latest set of raws, I found the following readme:

All files in this "raw" folder and its subfolders are released into the public domain:  to the extent permitted by law, we waive all copyright to them.  We will not pursue a copyright claim even if this waiver is not applicable in a given area.

Please consider attributing yourself or an alias if you distribute your own modifications so that they aren't confused with vanilla DF (it helps us in bug reports).

Just as an exercise in archival, I wanted to put up each version of the raws available here: http://www.bay12games.com/dwarves/older_versions.html on to Github. I would attribute them all to Toady One <toadyone@bay12games.com>. It would be best if Toady himself could do it, so that someone like me downloading all the appropriate versions doesn't consume all his bandwidth.

Does that sound valuable to anyone else besides me?

[Reelya]

GIT/GitHub is not an appropriate technology for merely storing already-completed files. It's "versioning" software in the sense that you can edit a single set of documents then roll back to a previous version if you screw something up. Using this merged-folder feature with the raws would just make a gigantic mess that's of no use to anyone, and putting each version in a separate folder would defeat the purpose of choosing to host them on GitHub.

In theory, you could learn how to use GitHub using Toady's raws (apply each version as an update one by one), but you'd learn more merely making your own project, and the resulting GitHub repo would be of no use to anyone: all the versions would be smooshed into a single folder and you'd have to specific rollback points to get it to give you specific versions to download. And since a specific set of raws may not even work without the correct matching df.exe, this is not useful.

Having Toady himself upload the versions to GitHub serves absolutely no purpose. This only has value as a personal learning exercise. And if you want to do that, try making your own project or raws mod, and hosting that on GitHub.

[Putnam]

GIT/GitHub is not an appropriate technology for merely storing already-completed files. It's "versioning" software in the sense that you can edit a single set of documents then roll back to a previous version if you screw something up. Using this merged-folder feature with the raws would just make a gigantic mess that's of no use to anyone, and putting each version in a separate folder would defeat the purpose of choosing to host them on GitHub.

It would be completely amazing for updating mod compatibility. file changes.txt is nice, but getting an actual diff of every single file change for every version would be much better.

[Bumber]

GIT/GitHub is not an appropriate technology for merely storing already-completed files. It's "versioning" software in the sense that you can edit a single set of documents then roll back to a previous version if you screw something up. Using this merged-folder feature with the raws would just make a gigantic mess that's of no use to anyone, and putting each version in a separate folder would defeat the purpose of choosing to host them on GitHub.

It would be completely amazing for updating mod compatibility. file changes.txt is nice, but getting an actual diff of every single file change for every version would be much better.

I don't think you need Git for that. I'm sure something could be set up on the DF wiki.

[GiantUrist]

I took the plunge and made the repository: https://github.com/tareqak/df_raws

The utility I used to make the repository is here: https://github.com/tareqak/df_raws_helper

[expwnent]

Neat!

[yxe]

great

[MobRules]

Awesome.

I also love how this simplifies updating modified raws when new official raws come out -- you can use git to see where all the merge conflicts would be, and resolve them.