cwilling / pvc Goto Github PK

Treatment of option could be better:

1. a command with just a --project option could specify multiple projects
   e.g. pvc show --project uTox live555 qwt
2. if a command only takes one particular option (like --project), then make it optional
   i.e. 'pvc show --project uTox' could just be 'pvc show uTox'

Need template for additional modules + description of what to do for new module

Needs a manpage

How about being able to specify an alternative watch list file. Always keep the default watch file but enable others to be used when specified with a -w|--watchlist option. They could be added with the config --add command e.g. "pvc config --add watch_alt1:/some/directory" would add a watchlist named watch_alt1.json in the chosen /some/directory (we better be able to write in there)

Is there a way to upgrade? Even 'npm uninstall pvc' then 'npm install pvc' didn't increment the version number...

Provide mechanism for installing as a system app i.e. 'make install DESTDIR=XXX'

Needs documentation

Current method of stripping non numeric characters from front and back of version id's doesn't work as expected for (at least) OpenImage/oiio archive at Github. That archive also contains other software with independent version numbering so just stripping text as currently done gives wrong results since we're (wrongly) mixing up the different softwares.

Retrieval of multipage output is sequential, as recommended by Github at https://developer.github.com/guides/traversing-with-pagination/. However this is slow when a particular archive has lots of pages e.g. OpenImageIO/oiio and collecting results async could be much faster.

Some github repos have lots of tag pages (vim has 192!) with mostly old releases that we're not interested in and consume lots of time. On the other hand some repos have lots of pages AND lots of different sotware under the same project's tags i.e. we need to keep looking until we find them

Need to limit the number of pages requested - maybe stop when version(s) equal or greater than what we have already?

d@cosmos:~$ pvc -V
PVC version
d@cosmos:~$

Wouldn't it be good if it can also update its own version, or is the user supposed to 'pvc update' pvc as well as everything?

One repository I'd like to write a module for is http://crawl.develz.org/release/ ... but I don't know JavaScript. The tutorial/example (using VLC) looks like it might work without any major changes... but I'm not really sure (don't know what a lot of the commands do.)

I added all my projects but noticed one said ‘undefined,’ since so far the programmer only uploaded version numbers using those ‘hashes’ rather than standard decimal version numbers... is there, or will there be, a way to specify you're checking those instead of, or in addition to, decimal number versions? It could be useful since hashed version numbers are all some projects do anymore.

Some requests to Github result in multiple pages of results. Need to support this case else wrong result (from first page only) is given.

What tokens would be best to use if you set this up as a cron job to check github--‘repo,’ ‘notifications?’