On 3/7/19 8:55 AM, Dennis Powless wrote:
> -do I NEED to uninstall Gnucash?
> If so....


I've been told that you need to do so. 

>
> I installed 3.1 from source, I now am trying to upgrade to 3.4.  On 18.04
> LTS.


Where did you do the build?  Do the "make uninstall" from that
directory/folder.

>
> I have on my home directory....
> dennis@dennis-XPS-8500:~/Applications$ ls
> build-gnucash-3.1  gnucash-3.1


Looks like ~/Applications/build-gnucash-3.1 is your build directory,
make uninstall while in that location.

>
>
>
>
> Output from whereis gnucash
> /home/dennis/.local/bin/gnucash
>
> I used
> Do I navigate to that location and run    make uninstall    ?
Not there.  The build directory where the make file is located.
>
>
>
>
>
>
>
> FYI:
> dennis@dennis-XPS-8500:~$ sudo apt list --installed | grep gnucash
> WARNING: apt does not have a stable CLI interface. Use with caution in
> scripts.
>
> sudo apt-get remove --purge gnucash
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Package 'gnucash' is not installed, so not removed
>
> sudo apt-get remove --purge gnucash
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Package 'gnucash' is not installed, so not removed
>
>
> d

That's the nature of a local build.  I'm getting into the habit of
building to a .deb file and installing from there.

--Steve

-- 
Stephen M Butler, PMP, PSM
[email protected]
[email protected]
253-350-0166
-------------------------------------------
GnuPG Fingerprint:  8A25 9726 D439 758D D846 E5D4 282A 5477 0385 81D8

_______________________________________________
gnucash-user mailing list
[email protected]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to