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

[feature request] make <pkg or .ipkg> optional #297

Closed
isberg opened this issue Jul 28, 2024 · 2 comments · Fixed by #298
Closed

[feature request] make <pkg or .ipkg> optional #297

isberg opened this issue Jul 28, 2024 · 2 comments · Fixed by #298
Labels
feature request Request for new functionality

Comments

@isberg
Copy link

isberg commented Jul 28, 2024

It would be handy if pack when not given an explicit package would look for a package in the current folder and use that. It would simplify scripts when doing continuous integration.

@isberg isberg changed the title Make <pkg or .ipkg> optional [feature request] make <pkg or .ipkg> optional Jul 28, 2024
@buzden
Copy link
Collaborator

buzden commented Jul 28, 2024

I'd love this too. But what do you think pack should do in the case of several ipkg files? Just throw an error of ambiguity?

@isberg
Copy link
Author

isberg commented Jul 28, 2024

Considering that you might have just forgot to specify the package, I guess it would make sense to show the help, similar to how it works now, but perhaps says it found multiple package and that it refuse to choose. But personally I would be happy enough if it just choose one, if the other option was to much work to implement.

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

Successfully merging a pull request may close this issue.

2 participants