You do this. Any found bug helps to improve it.
View attachment 529728
Oh boy! I got challenged.
I did'n say anything. Bummer. Nobody looks at the user signatures. Ever! Totally not my fault.
LisaRepacks did dig my app out and i developed it by pure accident. (Look in my
You must be registered to see the links
for this.)
to 1) Should? Hmp. Thats your choice.
Lets just say:
- Unrpa
- 8 formats/variants | 6 working
- [+] Its supports a good number of formats.
- [-] Got IMO less usable with the packaging and split to a dozen files.
- [-] It has two formats(RPA1/3.2) not working atm which i last year already reported.
- [+] Good extensible and OK maintainable.
- Rpatool
- 4 formats/variants | 3 working
- [+] Still works for RPA 2/3/3.2.
- [-] Its not really maintained anymore. Last change was adding RPA3.2 a year ago and by another user. Nearly 3 years for the main devs last activity.
- [-] RPA1 not working.
- [-] Adding other formats is cumbersome.
- RpaKit
- 8 formats/variants | 8 working
- [+] Supports every format except ZiX
- [+] Easily extensible
- [+] Takes also a directory with RPA as input(No manual feeding)
- [-] Still in alpha. Relatively untested "in the wild"; Has surely bugs. (A logical guess)
(Should i have added "+ Its shiny" for RpaKit?
)
to 2) Bah! I did simply add the license the advisor tool said. Laziness got me this.
I wanted just to open source it and that changes by others are stated, so people come not crying to me with the bulls**t of others. A somewhat security layer.
I switches it to Apache-2.
So. I opened it simply for others, because why not? People can test/use it, make bug reports, add stuff, improve my ugly code. And i learn some from it.
Next thing is, i want to add a second identifying run if it fails for a file and try to get it then still working. The ability to force a archive version like unrpa does could also be useful.
Greets