Linux Tools Project/News/NewIn60
- 1 All plugins
- 2 Docker Tooling
- 3 Oprofile
- 4 RPM
- 5 Systemtap
Added native touchpoints instructions so p2 checks whether the underlying tools (rpm, perf, oprofile..) are installed and if not give message to the user what is missing and what command to use to install it.
Support for all the content types with specialized editors is hooked into Eclipse 4.7 new generic editor. Not on par yet but it's first step towards removing all the specialized editors in the future. Users are advertised to try and report issues.
Editors (*.stp, Dockerfile, *.supp, *.spec, ChangeLog) highlighting colors are no longer hardcoded but defined in the plugin.xml file via org.eclipse.ui.themes extension point. Users of the dark theme are encouraged to contribute definitions to make it work better in it.
Update of Docker Client
The level of the underlying com.spotify.docker.client plug-in used to access the Docker daemon has been upgraded to 6.1.1.
New Security Options
Support has been added when launching commands in a Container to specify a security option profile. This can be done in lieu of specifying privileged mode. For example, to run gdbserver, one can specify "seccomp:unprofiled" to allow ptrace commands to be run by the gdb server.
The Run Image Wizard has been modified to allow specifying an unconfined seccomp profile to replace the default seccomp profile.
The security options are also now shown in the Properties View.
Many of the Linux Tools editors have been modified to use the new generic editor as a base.
Opcontrol support removed
Support for opcontrol based profiling has been removed. It is not shipped with oprofile for years and there was no easy way to verify it still works.
SpecfileEditor is no longer API
Decoupled the codebase from SpecfileEditor and make it non-api in preparation for totally replacing it with Generic Editor in the future.
Hyperlinks are created in the run console for navigation to *.stp or *.h/c files if paths to them are printed during the run.
Error view removed
It was used as a replacement for the missing console hyperlinks to make navigation possible to locations in the code where the error/warning appeared. Now that proper hyperlinks support is added this one is simply useless. Reduces confustion with PDE's Error view too.