Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider splitting out deployment functionality to a separate executable #29

Open
jheiss opened this issue Aug 17, 2012 · 0 comments
Open

Comments

@jheiss
Copy link
Member

jheiss commented Aug 17, 2012

The tpkg executable currently handles all of the local package operations as well as deployment to remote servers. The deployment functionality is rather different from the local package operation functionality in that it strips out any deployment-related command line options from the command line options that the user specified, then executes tpkg on the remote machines over ssh, replaying all the non-deployment options.

I haven't convinced myself one way or the other yet, but I think there's cause to believe we should move the deployment functionality to a separate executable (perhaps tdeploy?) The mechanism by which we strip out deployment-related options is fragile (see note in code comment for details) and would be hard to make robust. And more generally they seem like two different sets of functionality and having them in a single executable contributes to the overwhelming number of tpkg options and the general feeling that tpkg is too complex.

Was: https://sourceforge.net/apps/trac/tpkg/ticket/47

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant