- Joined
- Oct 27, 2002
- Messages
- 23,745
- Solutions
- 14
- Reaction score
- 13,764
- Trophies
- 4
- Age
- 48
- Location
- Engine room, learning
- XP
- 15,713
- Country
@midstor :
I'm not sure if all developers are happy you are making nsp files for their tool. it means static installed version, and hard to update.
You'll have to maintain creating these nsp every time there's a new revision or else there's no interest in doing any.
it seems tinfoil refuse to install a NSP if the titleID is already installed, and you need to delete it first, making it hard to update.
few things :
- marking this thread as release looks like you created and released something new, while it's not your work.
- ask the developer if they are fine with you creating a nsp for their homebrew first.
- Maybe the developer would prefer you release it on their threads instead, and maybe even make these nsp part of the official release (github, etc.), not provided by someone else on random forum threads. Maybe work with the devs to include nsp creation in their makefile.
- If you create lot of nsp, don't create a new thread for each programs, put all nsp in the same global nsp thread, maintain a list in first post.
- provide the homebrew version/revision/branch chksm used to create the nsp, because your nsp will be quickly outdated.
- if you create and release nsp, provide the titleID, gives proper information if it's a full title or a forwarder title, if it's a forwarder provide the path to the nro on SD card.... and update the wiki.
edit:
- Give credits where credit due !
which means if you release an nsp file, at least links to the official release thread because you are not the hmebrew author. at best, talk with the official author first.
Edit2:
Seeing other users are creating and releasing nsp, I think it would be better to just create and include a .txt file with the nsp.
that way, each nsp will be provided with proper information. Something like :
- nsp has name and titleID in the filename <homebrew name>_<titleID>_<additional text>.nsp
- nsp are packed to zip or rar (nsp extension can't be added to post anyway)
- an accompanying .txt file should be provided with the nsp
- .txt filename match the .nsp filename, so you can put multiple nsp in the same rar.
example :
Tinfoil - NSP Installer_01000A0000000001.nsp
Tinfoil - NSP Installer_01000A0000000001.txt
Tinfoil - NSP Installer_01000A0000000001_R.nsp
Tinfoil - NSP Installer_01000A0000000001_R.txt
nsp.txt could contain this:
This is open to discussion, let's find a good sharing method to prevent later conflicts and issues with nsp without provided information or version.
or, just release things like you want and let anarchy rule the switch scene. that's a valid method too. Who am I to control things, right?
I'm not sure if all developers are happy you are making nsp files for their tool. it means static installed version, and hard to update.
You'll have to maintain creating these nsp every time there's a new revision or else there's no interest in doing any.
it seems tinfoil refuse to install a NSP if the titleID is already installed, and you need to delete it first, making it hard to update.
few things :
- marking this thread as release looks like you created and released something new, while it's not your work.
- ask the developer if they are fine with you creating a nsp for their homebrew first.
- Maybe the developer would prefer you release it on their threads instead, and maybe even make these nsp part of the official release (github, etc.), not provided by someone else on random forum threads. Maybe work with the devs to include nsp creation in their makefile.
- If you create lot of nsp, don't create a new thread for each programs, put all nsp in the same global nsp thread, maintain a list in first post.
- provide the homebrew version/revision/branch chksm used to create the nsp, because your nsp will be quickly outdated.
- if you create and release nsp, provide the titleID, gives proper information if it's a full title or a forwarder title, if it's a forwarder provide the path to the nro on SD card.... and update the wiki.
edit:
- Give credits where credit due !
which means if you release an nsp file, at least links to the official release thread because you are not the hmebrew author. at best, talk with the official author first.
Edit2:
Seeing other users are creating and releasing nsp, I think it would be better to just create and include a .txt file with the nsp.
that way, each nsp will be provided with proper information. Something like :
- nsp has name and titleID in the filename <homebrew name>_<titleID>_<additional text>.nsp
- nsp are packed to zip or rar (nsp extension can't be added to post anyway)
- an accompanying .txt file should be provided with the nsp
- .txt filename match the .nsp filename, so you can put multiple nsp in the same rar.
example :
Tinfoil - NSP Installer_01000A0000000001.nsp
Tinfoil - NSP Installer_01000A0000000001.txt
Tinfoil - NSP Installer_01000A0000000001_R.nsp
Tinfoil - NSP Installer_01000A0000000001_R.txt
nsp.txt could contain this:
Code:
NSP info
=======
Homebrew name : <name of the homebrew>
nsp TitleID : <titleID>
nsp type : <Full | nro forwarder>
Homebrew version : <version of the homebrew if full nsp>, possibly even the corresponding github cheksum/link used to generate the nsp, or link to the .nro release page.
Forward to : not a forwarder | switch/path/to/filename.nro
nsp Creation date
nsp creation author
nsp packed with <tool name/version> if relevant info. in case some tool/version have future discovered bugs?
Credit
=====
homebrew link
homebrew authorThis is open to discussion, let's find a good sharing method to prevent later conflicts and issues with nsp without provided information or version.
or, just release things like you want and let anarchy rule the switch scene. that's a valid method too. Who am I to control things, right?
Last edited by Cyan,
