Gentoo ebuilds

maggu2810 · 09-19-2015, 11:36 AM

I started to write Gentoo ebuilds. The ebuilds are working for me, but I think they needs further inspection and tests:

https://github.com/maggu2810/maggu28...b49c5dbbcedb74

maggu2810 · 09-20-2015, 10:00 AM

I have missed to add the PM stuff, it is done now.

If the DisplayLinkManager ist installed to /usr/lib/displaylink the EDID files are created in /usr/lib.
So I changed the directory layout.

Which directories need to be writable / readable by the DisplayLinkManager?
I would like to use a separate user for running this executable, running such stuff as root is IMHO not a solution.

maggu2810 · 09-20-2015, 10:52 AM

Installed:

Code:

/opt/displaylink/manager/LICENSE
/opt/displaylink/manager/firefly-monitor-release.spkg
/opt/displaylink/manager/ella-dock-release.spkg
/opt/displaylink/manager/DisplayLinkManager

started: /opt/displaylink/manager/DisplayLinkManager
working dir: /opt/displaylink_wdir/manager

created at runtime:

Code:

/opt/displaylink/manager/DisplayLinkManager.log
/opt/displaylink/manager/FirmwareTrace.log
/opt/displaylink/managerHanns.G HG281_HSD1CF3-922LB3QA01119.edid
/opt/displaylink_wdir/manager/PmMessagesPort_in
/opt/displaylink_wdir/manager/PmMessagesPort_out
/opt/displaylink_wdir/manager/DLInstrumentationDirectoryLock

That files are created in the working directory is fine, we could set it to /var/displaylink or something similar. That information does not need to be persistent.

IMHO:
Nothign should be stored in the directory of the DisplayLinkManager binary.
The log files should be placed in the working directory, too.
Also the EDID should be stored in the working directory (does not know if the path separtor '/' is missing).

gaya · 10-20-2015, 01:30 PM

It works pretty nice. In my setup I can use the 2 TVs connected via the two HDMI ports. DP is not tested by me.
However, to install the ports I had to change the ebuild RDEPEND:
/var/lib/layman/maggu2810-overlay/x11-drivers/displaylink-driver/displaylink-driver-1.0.138-r1.ebuild

RDEPEND="virtual/libusb:1
x11-video/evdi"

->
RDEPEND="virtual/libusb:1
x11-drivers/evdi"

because there is no x11-video
Then I could add the "displaylink" service with systemctl and add the evdi module to evid.conf in the /etc/modules-load/evdi.conf ("evdi").

Thank you!

maggu2810 · 11-10-2015, 06:54 PM

Thank you.
I fixed that, perhaps you could write me a E-Mail next time, so I does not loose your hint.

09-19-2015, 11:36 AM	#1
maggu2810 Junior Member Join Date: Sep 2015 Posts: 7	Gentoo ebuilds I started to write Gentoo ebuilds. The ebuilds are working for me, but I think they needs further inspection and tests: https://github.com/maggu2810/maggu28...b49c5dbbcedb74

09-20-2015, 10:52 AM	#3
maggu2810 Junior Member Join Date: Sep 2015 Posts: 7	Installed: Code: /opt/displaylink/manager/LICENSE /opt/displaylink/manager/firefly-monitor-release.spkg /opt/displaylink/manager/ella-dock-release.spkg /opt/displaylink/manager/DisplayLinkManager started: /opt/displaylink/manager/DisplayLinkManager working dir: /opt/displaylink_wdir/manager created at runtime: Code: /opt/displaylink/manager/DisplayLinkManager.log /opt/displaylink/manager/FirmwareTrace.log /opt/displaylink/managerHanns.G HG281_HSD1CF3-922LB3QA01119.edid /opt/displaylink_wdir/manager/PmMessagesPort_in /opt/displaylink_wdir/manager/PmMessagesPort_out /opt/displaylink_wdir/manager/DLInstrumentationDirectoryLock That files are created in the working directory is fine, we could set it to /var/displaylink or something similar. That information does not need to be persistent. IMHO: Nothign should be stored in the directory of the DisplayLinkManager binary. The log files should be placed in the working directory, too. Also the EDID should be stored in the working directory (does not know if the path separtor '/' is missing).

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

09-20-2015, 10:00 AM	#2
maggu2810 Junior Member Join Date: Sep 2015 Posts: 7	I have missed to add the PM stuff, it is done now. If the DisplayLinkManager ist installed to /usr/lib/displaylink the EDID files are created in /usr/lib. So I changed the directory layout. Which directories need to be writable / readable by the DisplayLinkManager? I would like to use a separate user for running this executable, running such stuff as root is IMHO not a solution.

10-20-2015, 01:30 PM	#4
gaya Junior Member Join Date: Jul 2015 Posts: 3	It works pretty nice. In my setup I can use the 2 TVs connected via the two HDMI ports. DP is not tested by me. However, to install the ports I had to change the ebuild RDEPEND: /var/lib/layman/maggu2810-overlay/x11-drivers/displaylink-driver/displaylink-driver-1.0.138-r1.ebuild RDEPEND="virtual/libusb:1 x11-video/evdi" -> RDEPEND="virtual/libusb:1 x11-drivers/evdi" because there is no x11-video Then I could add the "displaylink" service with systemctl and add the evdi module to evid.conf in the /etc/modules-load/evdi.conf ("evdi"). Thank you!

11-10-2015, 06:54 PM	#5
maggu2810 Junior Member Join Date: Sep 2015 Posts: 7	Thank you. I fixed that, perhaps you could write me a E-Mail next time, so I does not loose your hint.