-
Notifications
You must be signed in to change notification settings - Fork 1
Description
So that's yet another thing I want to implement in Urcheon since the very beginning but that always got de-prioritized because of other things like things actually needed to build a release.
The idea is that someone could do this:
mkdir package_src.dpkdir
cd package_src.dpkdir
urcheon --game unvanquished initOr:
urcheon --game unvanquished init package_src.dpkdirThis would set up the basic configuration of an urcheon-driven dpkdir, here it's just about writing unvanquished in package_src.dpkdir/.urcheon/game.txt and may be write a default .gitignore.
This would also be doable:
urcheon --game unvanquished init --git package_src.dpkdirThis would create the dpkdir folder, write the configuration, call git init and commit the basic things.
For collections (like UnvanquishedAssets or InterstellarOasis parent directories), one would just do that:
mkdir MyAssets
cd MyAssets
urcheon init --collectionor
urcheon init --collection MyAssetsAnd of course that would be possible as well:
urcheon init --collection --git MyAssets
Writing the game name in the collection configuration would allow to not have to retype it when creating dpkdirs.
So a complete git-based scenario would be:
urcheon --game unvanquished init --collection --git MyAssets
cd MyAssets
urcheon init --git src/package0_src.dpkdir
urcheon init --git src/package1_src.dpkdir
urcheon init --git src/package2_src.dpkdir
This would be the same as:
mkdir MyAssets
cd MyAssets
urcheon --game unvanquished init --collection --git
urcheon init --git src/package0_src.dpkdir
urcheon init --git src/package1_src.dpkdir
urcheon init --git src/package2_src.dpkdir