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

Would you consider renaming this tool or making it compatible with the one in Debian? #2

Open
sto opened this issue Aug 4, 2023 · 4 comments

Comments

@sto
Copy link

sto commented Aug 4, 2023

Hi, first of all let me tell you that I find this tool quite useful, so thanks for writing it!

As I've been using it lately I decided that including it on the debian repository would be a good idea, but after filling the ITP I noticed that there is already a tool with the same name on the archive.

I could package it with a different name for Debian, but if you change the name upstream we would be in sync.

Just think about it, I guess a name like gotmpl would also be good and a little bit clearer, but any name that does not create conflicts is good for me.

If you don't want to rename your tool it's OK, but I will have to do it for the debian package, so in any case I would like your input on the name to use.

@andrewshadura
Copy link

Alternatively, how about adding support for command-line options offered by that other tmpl tool?

$ echo '["foo","bar","baz"]' > tmpldata
$ tmpl -data=@tmpldata my.tmpl

@sto
Copy link
Author

sto commented Aug 5, 2023

Alternatively, how about adding support for command-line options offered by that other tmpl tool?

$ echo '["foo","bar","baz"]' > tmpldata
$ tmpl -data=@tmpldata my.tmpl

yes, that would work too, sure, in fact if you do that we can replace the other tool

@sto
Copy link
Author

sto commented Aug 6, 2023

Although I'm not really a golang programmer I've taken the liberty to create a PR to make your tool compatible with the one in Debian.

If you integrate my changes or an updated version of them in your repository I'll be able to package your upstream source as is because it provides a full replacement of the old command.

@sto sto changed the title Would you consider renaming this tool? Would you consider renaming this tool or making it compatible with the one in Debian? Aug 6, 2023
@sto
Copy link
Author

sto commented Sep 12, 2023

Any news about this? Have you given it any thought?
I'm waiting for an answer to create and upload the package to Debian.

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

No branches or pull requests

2 participants