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

Directly use NoPayStation format .tsv files for pkgi #8

Open
arromdee opened this issue Oct 25, 2017 · 4 comments
Open

Directly use NoPayStation format .tsv files for pkgi #8

arromdee opened this issue Oct 25, 2017 · 4 comments

Comments

@arromdee
Copy link

See subject. Of course, using such files would mean having to ignore lines that don't have licenses, etc.

@mmozeiko
Copy link
Owner

mmozeiko commented Oct 25, 2017

No. There are too many disadvantages.

  1. No pkg sizes
  2. No original game names (for Japanese games & similar)
  3. No sha256
  4. No other info I want to add in next releases (like game category - Arcade, RPG, ...)
  5. Much more data needs to be downloaded and processed, filter out MISSING, 3.61+, etc...
  6. pkgi will be tied to format that is not fixed, any bigger change in NPS (spreadsheet rename, column rearrangement) and app will break.

@Dimensional
Copy link

NoPaystation would simply need to add those necessary parts and keep it's formatting the same. Though a tsv is suppose to be tab separated values, which isn't as easy to read in some places as csv, which pkgi already is formatted to potentially read.

Repository owner deleted a comment from TheRadziu Nov 19, 2017
@mmozeiko
Copy link
Owner

No links to sites with content that has zRIF please.

@TheRadziu
Copy link

You should tell me to edit it out. Anyway no point in this 'issue', since there is tool for that (and you did not want to use NoPayStation directly anyway)

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

4 participants