You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 init
This 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.
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 init
Or:
This would set up the basic configuration of an urcheon-driven dpkdir, here it's just about writing
unvanquished
inpackage_src.dpkdir/.urcheon/game.txt
and may be write a default.gitignore
.This would also be doable:
This 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 --collection
or
And of course that would be possible as well:
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:
This would be the same as:
The text was updated successfully, but these errors were encountered: