Index | Thread | Search

From:
Kirill A. Korinsky <kirill@korins.ky>
Subject:
Re: [NEW] net/b2
To:
Paul Galbraith <paul@galbraiths.ca>
Cc:
Stuart Henderson <stu@spacehopper.org>, Abel Abraham Camarillo Ojeda <acamari@verlet.org>, A Tammy <openbsd.ports@aisha.cc>, ports@openbsd.org
Date:
Sun, 04 Aug 2024 12:19:58 +0200

Download raw body.

Thread
On Sat, 03 Aug 2024 22:24:00 +0200,
Paul Galbraith <paul@galbraiths.ca> wrote:
> 
> This is what I have been using now, it seems ok to me:
>

I haven't tested it, just make a quick read. Plan to test in soon.

Anywa, PLIST contians:

  bin/backblaze-b2
  bin/backblaze-b2v3
  bin/backblaze-b2v4

so, scripts which is started as

  #!/usr/bin/env b2v3

should be rewritten to

  #!/usr/bin/env backblaze-b2v3

and so on.

I not sure that it is widley used, but it may create some headache if
someone would like to share this scripts with debian where b2v3 without
backblaze- prefix. Or when someone migrated his scripts from b2 which was
intalled via something like pipx

But, again, this is edge case. I not sure how many users hit it.

From another hand backblaze- prefix make things cleaner, and I can live with
it by trivial migration for the only script which I have.

-- 
wbr, Kirill