Hi,
It happens that I'd like to "install" a variant of a self-built port without
actually activating it (e.g. when libraries are in use and I have no immediate
need to activate that different variant).
Looking through the code I saw there must exist a `port archive` comm
ough the code I saw there must exist a `port archive` command that
> isn't documented in the manpage. Does that do what I'm looking for or does it
> just make the tar bundle under $prefix/var/macports/software ?
Yes, 'port archive' would do what you are looking for.
On Sunday October 22 2023 19:38:46 Rainer Müller wrote:
>Yes, 'port archive' would do what you are looking for. You are correct
>this is actually missing in port(1), but please see the separate man
>page port-archive(1).
Thanks, and strange. That's exactly what I did, o
> no immediate need to activate that different variant).
> >
> > Looking through the code I saw there must exist a `port archive` command
> > that isn't documented in the manpage. Does that do what I'm looking for or
> > does it just make the tar bundle under $pre
On Monday October 23 2023 01:34:03 Eric Gallager wrote:
>I sometimes try using the `port archive` command, and one thing I'm
>wondering about it is, why does it bother calculating conflicts if it
>doesn't actually install the port?
That's strange, in my experience con
FWIW, I'm now using `port archive` in my "devport" PortGroup, so that updating
the main port and the companion devport with developer content doesn't
re-activate that content if the user deactivated it. (It still gets installed
normally otherwise.)
R.
On Mon, Oct 23, 2023 at 7:29 AM René J.V. Bertin wrote:
>
> On Monday October 23 2023 01:34:03 Eric Gallager wrote:
>
> >I sometimes try using the `port archive` command, and one thing I'm
> >wondering about it is, why does it bother calculating conflicts if it
>
ps://guide.macports.org/#project.tickets if you
>believe there is a bug.
Heh, at least it's telling you what to do ;)
Allowing `port archive --force foo` to override/ignore such conditions should
be an acceptable workaround I suppose?
Compare to dpkg's --force-X options.
R.
