andrew-vant / romtool

A game-independent ROM editing tool
0 stars 0 forks source link

Figure out repo structure and packaging before public release #36

Open andrew-vant opened 6 years ago

andrew-vant commented 6 years ago

Packages needed: pip, rpm, deb, msi.

Components needed: romlib, romtool, maps.

Question: Should romlib, romtool, and maps be separate repos?

Observations: on deb/rpm systems, there's a case for making the packages separate; on windows systems with no dep management, there should probably be one .msi package. Should that package contain the maps, or offer to download them as part of the install perhaps?

Observations 2: Updates to provided map packages may break projects in progress. How to ensure old maps are still available? The user would have to keep a local copy of it in their project dir and map path. Is there a good way to automate that? Have some subdir of the local dir included in map search, and a subcommand for project init that copies the appropriate map? But a local cached map is subject to breaking if romlib is updated (But that may be preferable to not having it available at all; user can always downgrade again, right?)

Observations 3: There's a dependency tree here. Maps have a dependency on certain romlib versions. Projects have a dependency on certain map versions. What else am I missing?