Bug 222206 - [NEW PORT] x11/mons a shell script to manage monitors using xrandr
Summary: [NEW PORT] x11/mons a shell script to manage monitors using xrandr
Status: In Progress
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Mateusz Piotrowski
URL: https://reviews.freebsd.org/D18437
Keywords: patch
Depends on:
Blocks:
 
Reported: 2017-09-10 22:19 UTC by Robert James Hernandez
Modified: 2018-12-05 17:53 UTC (History)
3 users (show)

See Also:


Attachments
Mons Port Diff (3.10 KB, patch)
2017-09-10 22:19 UTC, Robert James Hernandez
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Robert James Hernandez 2017-09-10 22:19:31 UTC
Created attachment 186236 [details]
Mons Port Diff

This is a port of mons 0.6.2: https://github.com/Ventto/mons which is a shell script to quickly manage multiple monitors.

It's been a useful tool for my laptop since I'd rather not have to install a GUI app and all the dependencies just to mirror my laptop display with the projector.

Please let me know if there's anything I missed, this is my first port!

~Rob
Comment 1 Robert James Hernandez 2017-11-15 18:02:28 UTC
Anyone mind taking a look at this?
Comment 2 Niclas Zeising freebsd_committer 2018-02-11 14:11:11 UTC
I'm not sure why it was added to x11@, but I'll have a look at it.
Comment 3 Robert James Hernandez 2018-02-15 06:47:44 UTC
Hi Niclas,

This port is dependent on xrandr which was why I thought it belonged in x11@. If you would like me to move it to another section of ports just let me know!

~Rob
Comment 4 Niclas Zeising freebsd_committer 2018-02-15 19:00:33 UTC
Hi!
The category x11 is correct.  I was referring to this PR being assigned to the x11@ team.  The x11@ team is the maintainers of the core xorg ports, but this PR can be handled by anyone.
I hope this explanation makes it a bit clearer.
Apologies if I came off as a bit harsh in my previous comment.
Comment 5 Robert James Hernandez 2018-02-16 16:55:21 UTC
Ahh gotcha, well I appreciate you taking a look at this even though it ended up on the wrong list!

And don't worry, it didnt come off harsh at all. I just wanted to make sure it was clear why I place it in the x11 section of ports.
Comment 6 Tobias Kortkamp freebsd_committer 2018-12-05 14:56:15 UTC
Assignee timeout. Give back to pool.
Comment 7 Mateusz Piotrowski freebsd_committer 2018-12-05 17:19:21 UTC
Let's try to upstream some patches not to pollute the tree unnecessarily: https://github.com/Ventto/mons/issues/30
Comment 8 Robert James Hernandez 2018-12-05 17:53:18 UTC
Thanks for picking this up Mateusz! I like the idea of fixing the hardcoding paths in upstream.

Im happy to work with you to get this added to ports as well.