On Sun, Apr 21, 2024 at 05:32:37PM +, Mathias Gibbens wrote:
> I like that idea, thanks! It would be easy enough to add that to
> Incus' $PATH while making it simple for an end user to modify their
> local environment to directly use `mc` if they wish.
Let me express a concern regarding this
On Thu, 2025-03-06 at 06:58 +0100, Helmut Grohne wrote:
> On Sun, Apr 21, 2024 at 05:32:37PM +, Mathias Gibbens wrote:
> > I like that idea, thanks! It would be easy enough to add that to
> > Incus' $PATH while making it simple for an end user to modify their
> > local environment to directl
On Wed, Apr 24, 2024 at 9:42 AM Andreas Tille wrote:
> Am Mon, Apr 22, 2024 at 09:28:29AM +0200 schrieb Philip Hands:
> > >> /usr/libexec/minio-client/bin/mc -> /usr/bin/mcli
> >
> > Might I suggest that the link goes the other way, so that the symlink
> > lives in /usr/bin? That way the existenc
Hi,
Am Mon, Apr 22, 2024 at 09:28:29AM +0200 schrieb Philip Hands:
> >> /usr/libexec/minio-client/bin/mc -> /usr/bin/mcli
>
> Might I suggest that the link goes the other way, so that the symlink
> lives in /usr/bin? That way the existence of the lib directory is
> somewhat self-documenting.
Th
Am 21.04.2024 um 18:31 schrieb Mathias Gibbens:
Currently, Midnight Commander is packaged for Debian as `mc`. I am
looking at packaging the MinIO Client (needed for a future release of
Incus), which also unfortunately names its binary `mc`. MinIO upstream
has been pretty clear that they don't
* Simon McVittie [240422 05:02]:
> On Mon, 22 Apr 2024 at 09:44:12 +0200, Simon Josefsson wrote:
> > Philip Hands writes:
> > > Might I suggest that the link goes the other way, so that the symlink
> > > lives in /usr/bin? That way the existence of the lib directory is
> > > somewhat self-docume
On Sun Apr 21, 2024 at 5:37 PM BST, Marco d'Itri wrote:
> Go for it, I think that there is no good solution for this case.
> Everybody who cares then will manually create a mc -> mcli symlink.
Indeed, they will: so I would suggest that the chosen binary name for
minio-client should *not* be mcli,
On Mon, 22 Apr 2024 at 09:44:12 +0200, Simon Josefsson wrote:
> Philip Hands writes:
> > Might I suggest that the link goes the other way, so that the symlink
> > lives in /usr/bin? That way the existence of the lib directory is
> > somewhat self-documenting.
Having the real executable in /usr/l
Philip Hands writes:
> Mathias Gibbens writes:
>
>> On Sun, 2024-04-21 at 18:47 +0200, Simon Josefsson wrote:
> ...
>>> /usr/libexec/minio-client/bin/mc -> /usr/bin/mcli
>
> Might I suggest that the link goes the other way, so that the symlink
> lives in /usr/bin? That way the existence of the
Mathias Gibbens writes:
> On Sun, 2024-04-21 at 18:47 +0200, Simon Josefsson wrote:
...
>> /usr/libexec/minio-client/bin/mc -> /usr/bin/mcli
Might I suggest that the link goes the other way, so that the symlink
lives in /usr/bin? That way the existence of the lib directory is
somewhat self-docu
On Sun, 2024-04-21 at 18:47 +0200, Simon Josefsson wrote:
> Marco d'Itri writes:
>
> > On Apr 21, Mathias Gibbens wrote:
> >
> > > While that might work for them, it obviously doesn't at a higher
> > > packaging level. Per Policy Section 10.1, I'm bringing this to d-devel
> > > for any commen
Marco d'Itri writes:
> On Apr 21, Mathias Gibbens wrote:
>
>> While that might work for them, it obviously doesn't at a higher
>> packaging level. Per Policy Section 10.1, I'm bringing this to d-devel
>> for any comments or suggestions on my plan for packaging the MinIO
>> Client. Following wh
On Apr 21, Mathias Gibbens wrote:
> While that might work for them, it obviously doesn't at a higher
> packaging level. Per Policy Section 10.1, I'm bringing this to d-devel
> for any comments or suggestions on my plan for packaging the MinIO
> Client. Following what several other distributions
13 matches
Mail list logo
