[MacPorts] #65825: Add i3status Portfile
MacPorts
noreply at macports.org
Mon Sep 12 02:38:51 UTC 2022
#65825: Add i3status Portfile
--------------------------+--------------------
Reporter: jenstroeger | Owner: (none)
Type: enhancement | Status: new
Priority: Normal | Milestone:
Component: ports | Version: 2.7.2
Resolution: | Keywords:
Port: i3 |
--------------------------+--------------------
Old description:
> Following up on ticket [https://trac.macports.org/ticket/65811 65811],
> and in particular [https://trac.macports.org/ticket/65811#comment:7 this
> comment]: the `i3wm` window manager ([https://ports.macports.org/port/i3/
> i3 port]) uses [https://github.com/i3/i3status i3status] by default to
> render data into its toolbar (managed by the `i3bar` tool). That
> `i3status` currently has no port.
>
> I’m actually tempted to add `i3status` to the `i3wm` port because of
> their close dependency, instead of adding a new port. That would make
> testing and installing easier—running `i3wm` would work out of the box
> without needing another port.
>
> Thought?
New description:
Following up on ticket:65811, and in particular [comment:ticket:65811:7
this comment]: the `i3wm` window manager
([https://ports.macports.org/port/i3/ i3 port]) uses
[https://github.com/i3/i3status i3status] by default to render data into
its toolbar (managed by the `i3bar` tool). That `i3status` currently has
no port.
I’m actually tempted to add `i3status` to the `i3wm` port because of their
close dependency, instead of adding a new port. That would make testing
and installing easier—running `i3wm` would work out of the box without
needing another port.
Thought?
--
Comment (by ryandesign):
The easiest course of action depends on how i3status is intended to be
built. If it is intended to be built by integrating its source code into
the i3wm source code, and then building i3wm causes i3status to be built,
then yes, adding i3status to the i3wm port may be the thing to do. If, on
the other hand, i3status is, like most software, separately buildable and
installable, then a separate portfile is most likely the thing to do.
--
Ticket URL: <https://trac.macports.org/ticket/65825#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list