A lot of Modern:tm: Package Managers have this magical init command to help people create an initial package-information file interactively. It might be a good idea to make one for the tree thing we have too.
A wizard should be able to ask for and fill in:
Package name and version
Package section (abbs tree and PKGSEC); with tab completion
Package source type selection (tbl, vcs, dummy)
Automatic addition of checksum
Package description
PKGDEP and BUILDDEP; with tab completion
I recommend using the readline library in Python. It's the old GNU readline with all the Emacs navigation shortcuts, quite useful for moving around "words" in the DEPS. And it seems to allow custom completers.
User story: Look at me. I am that one user, I am dumb and clumsy, and I can't edit text on a high-latency connection. Seriously, I found myself struggling over something this easy.
It would also be great to have a command for adding or removing DEPs for trial-and-error building. That would require reading the file though.
A lot of Modern:tm: Package Managers have this magical
initcommand to help people create an initial package-information file interactively. It might be a good idea to make one for the tree thing we have too.A wizard should be able to ask for and fill in:
I recommend using the
readlinelibrary in Python. It's the old GNU readline with all the Emacs navigation shortcuts, quite useful for moving around "words" in the DEPS. And it seems to allow custom completers.User story: Look at me. I am that one user, I am dumb and clumsy, and I can't edit text on a high-latency connection. Seriously, I found myself struggling over something this easy.
It would also be great to have a command for adding or removing DEPs for trial-and-error building. That would require reading the file though.