-
Notifications
You must be signed in to change notification settings - Fork 69
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
opkg support #62
Comments
Hi @arnottcr, I will take a look . |
Porting |
While I agree it would add complexity, you could have a vanilla POSIX header that determines the shell and then code paths for each major subgroup. I would imagine that this within the realm of what I am capable of, so if I get time I may submit a pull request, or be back with comments/questions. Also, from what I have seen bash is great for interactivity, but not the fastest at executing POSIX scripts, so there could be merit in migrating to a pure POSIX implementation of pacapt. (I agree it is odd that wget does not support tls, then again most package managers I have worked with, pacman included, prefer http and signatures over https.) |
@arnottcr pacapt code base relied heavily on non-POSIX shell features, example process substitution, It need a big effort to porting it to a POSIX implementation. |
@Gnouc, thanks; I have not looked in depth at the pacapt codebase, but that seems quite reasonable. [sarcasm] I will submit a pull request when I have all the porting done. [/sarcasm] |
I think it's good to start new branch, e.g, |
@arnottcr @Gnouc
I will take a look how the application can be built on |
@arnottcr |
Due to wrong linking the ticket was closed automatically. I reopen it now. Thanks. |
A quite complete Please help to review PR and I'll release them next week. Thanks. |
I'm happy to release new version Enjoy edit: fix typ0 |
It would be awesome if you could add support for opkg.
The text was updated successfully, but these errors were encountered: