You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think we should add bpkg for our lib's if we only want that a lib will be used on a server, instead of sharing the lib with all projects.
We will keep .deb for installing packages global, for examples packages in yosh, instead of installing it in the application.
Even with this we can install a system wide yosh. We should just see to get better solutions, urlencode, uuidgen, etC... we should use only BASH. so there will be no depend.
For example, if only want beanstalk client on esm instead of all others
project on the same host using yosh, we can simply update projects in on
project. Even when working on local for testing and working it simpler if
we have diffetents os.
I think we should add bpkg for our lib's if we only want that a lib will be used on a server, instead of sharing the lib with all projects.
We will keep .deb for installing packages global, for examples packages in yosh, instead of installing it in the application.
Even with this we can install a system wide yosh. We should just see to get better solutions, urlencode, uuidgen, etC... we should use only BASH. so there will be no depend.
Link to packaging System.
https://github.com/bpkg/bpkg
The text was updated successfully, but these errors were encountered: