Opened 21 months ago
Last modified 19 months ago
#65825 new enhancement
Add i3status Portfile — at Version 1
| Reported by: | jenstroeger (Jens Troeger) | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.7.2 |
| Keywords: | Cc: | ||
| Port: | i3 |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Following up on ticket:65811, and in particular this comment: the i3wm window manager (i3 port) uses 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?
Change History (1)
comment:1 Changed 21 months ago by ryandesign (Ryan Carsten Schmidt)
| Description: | modified (diff) |
|---|
Note: See
TracTickets for help on using
tickets.
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.