Re: gopasspw packaging (#901133)
On 2020, ജനുവരി 17 1:07:54 PM IST, "Balasankar "Balu" C" <firstname.lastname@example.org> wrote:
>On 30/3/19 8:01 PM, Balasankar C wrote:
>> Hi all, I am interested in packaging gopasspw, and have marked the
>corresponding bug(#901133) to an ITP.
>> I have written a few Go programs as hobby projects, but am new to
>packaging (I usually package Ruby libraries).
>> So, any help is much appreciated.
>After few months, I finally found some time to pick it back up. The
>remaining dependencies of gopasspw are
>I plan to package github-releases soon once its own dependencies are in
>vault is a bit big and a bit tricky. gopasspw does not require the
>entire vault codebase, but parts of it.
>Specifically things from api and sdk directories.
We discussed about packaging only part of bigger repos recently and agreed on packaging parts, just package vault-api and vault-sdk.
>So for now, I am thinking of keeping vault related stuff bundled in the
>source of gopasspw for building
>instead of attempting to package vault completely. How does the team
>feel about that?
>If bundling is absolutely not an option and vault must be packaged, I
>would need help from others to complete that.
>I've pushed my current plan to Salsa, bundling vault stuff. It
>doesn't build yet, but had to start
Sent from my Android device with K-9 Mail. Please excuse my brevity.