Re: [Jack-Devel] How to profile jack cpu load?

PrevNext  Index
DateSat, 14 Jul 2018 15:21:25 -0400
From Tim <[hidden] at rogers dot com>
To[hidden] at lists dot jackaudio dot org
In-Reply-ToChris Caudle Re: [Jack-Devel] How to profile jack cpu load?
Follow-UpChris Caudle Re: [Jack-Devel] How to profile jack cpu load?
On 07/14/2018 02:47 PM, Chris Caudle wrote:
> On Sat, July 14, 2018 11:52 am, Tim wrote:
>> Two versions of Jack can happily coexist - one in /usr
>>    and one in /usr/local.
> 
> Paul always warned strongly against that.  How do you make sure the one in
> usr is not used?

It should be automatic.
All user-built software is usually installed in /usr/local.
Most systems automatically look in /usr/local/bin FIRST
  before /usr/bin when you type an un-pathed program name

This makes it very easy to run your own builds of software while
  NOT disturbing the packaging system's installed versions in any way.

I routinely run my built versions of jack-1 or jack-2 installed in
  /usr/local, all while my distro's jack-2 package installation sits
  undisturbed in /usr. When I want to go back to the packaged version,
  I simply uninstall my built version, that MUST be done, to go back.

This is how I helped debug jack-1 and jack-2 at the same time.

Cheers.
Tim.

> The recommendation I had always heard when using something like Fedora
> which would try to remove a lot of packages if you removed the system
> provided RPM was to just delete the files manually, without touching the
> RPM database, then install the locally built version.
> Maybe you found a method that works reliably, but in the past at least
> even the jackd developers wouldn't trust leaving the distribution provided
> files on the filesystem.
> 
PrevNext  Index

1531596113.19522_0.ltw:2, <62eb2787-f1ab-ca84-52a3-4c77c6be6a85 at rogers dot com>