Locate uses a database that's generated periodically (typically weekly) from
cron. If you've deleted files since the last time it updated the database
you'll get files that aren't there any more. You can run
sudo locate.updatedb
to regenerate. It scans all of storage traversing filesystem mounts so be
prepared for it to take a long time.
Also notice that locate matches every path matching the pattern and if the
pattern contains no globbing characters locate treats it as *pattern*, i.e. it
matches any path with "pattern" (or in your instant case, "gnucash") anywhere
in it.
I already told you how to delete all of the gnucash-installed files in .local:
find ~/.local -name gnucash -o -name *gnc* -exec rm -rf {} \;
Regards,
John Ralls
> On May 3, 2019, at 1:34 PM, Dennis Powless <dpowless...@pobox.com> wrote:
>
> When I run.... locate gnucash in terminal I get 1,000's of lines.
>
> However, when I navigate to some of them some are empty (even with show all
> files checked).
>
> /home/dennis/.local/etc/gnucash/environment
> /home/dennis/.local/share/doc/gnucash/ChangeLog.1999
> /home/dennis/.local/share/gnucash/scm/gnucash/report/standard-reports/test/test-standard-category-report.scm
> /home/dennis/Applications/share/locale/ca/LC_MESSAGES/gnucash.mo
> /home/dennis/.local/lib/gnucash/scm/ccache/2.0/gnucash/gnc-modules/test/test-gnc-module-scm-init.go
> /home/dennis/Applications/libgnucash/tax/us/CMakeFiles/scm-tax-us.dir/DependInfo.cmake
> /home/dennis/.local/lib/gnucash/libgncmod-bi-import.so
> /home/dennis/.local/include/gnucash/SX-book.h
>
> Here is a few of the directories and files.... each one has numerous.
>
> What can I delete?
>
> dennis@dennisLaptop1:~$ whereis gnucash
> gnucash:
>
>
> D
>
> On Fri, May 3, 2019 at 4:26 PM John Ralls <jra...@ceridwen.us> wrote:
> So you built in the parent directory of the sources. Not exactly recommended
> but at least it's not the source directory itself.
>
> What files are left?
>
> Regards,
> John Ralls
>
> > On May 3, 2019, at 1:16 PM, Dennis Powless <dpowless...@pobox.com> wrote:
> >
> > I was able to run make uninstall on the Applications directory.
> >
> > The terminal completed the task.
> >
> > However, there seems to be still files hanging around.
> >
> > d
> >
> > On Fri, May 3, 2019 at 4:07 PM Dennis Powless <dpowless...@pobox.com> wrote:
> >
> >> dennis@dennisLaptop1:~$ locate cmake_uninstall.cmake
> >> /home/dennis/.local/share/Trash/files/gnucash-maint/cmake/
> >> cmake_uninstall.cmake.in
> >> /home/dennis/Applications/cmake_uninstall.cmake
> >> /home/dennis/Applications/gnucash-3.1/cmake/cmake_uninstall.cmake.in
> >>
> >> Can I then run the cmake uninstall from this location?
> >>
> >> d
> >>
> >> On Thu, May 2, 2019 at 9:40 PM David Cousens <davidcous...@bigpond.com>
> >> wrote:
> >>
> >>> John,
> >>>
> >>> Won't that simply remove the source directories. With that prefix Dennis
> >>> has
> >>> installed under /home/dennis/.local. If the build directory is under
> >>> ~/Applications/gnucash-3.1 then he will lose the manifest by using rm -rf
> >>> on the source directory.
> >>>
> >>> If he can locate the original build directory then issuing make uninstall
> >>> from a terminal open in that directory. I have adopted the practice of
> >>> putting the build directory inside the source directory and retaining both
> >>> (I once found that the make uninstall procedure seems to reference the
> >>> source directories not simply the manifest file or the build directories
> >>> but
> >>> I have never checked this out fully) until after I have removed a build.
> >>> It
> >>> doesn't cause any problems and keeps everything you need for an uninstall
> >>> together.
> >>>
> >>> Dennis
> >>> Your build directory is unlikely to be gnucash-3.1, that is most likely
> >>> the
> >>> source directory. Where it is located is the directory from which you
> >>> originally executed the cmake command since you used absolute addressing
> >>> to
> >>> the source. It may be inside gnucash-3.1 if you used the mkdir <build>
> >>> and
> >>> cd <build> commands from the terminal open atgnucash-3.1 before issuing
> >>> the
> >>> make command. Here <build> is a generic notation for a filename for a
> >>> build
> >>> file. It will have whatever name you gave it at the time. The attached
> >>> screenshot gives you the directory structure and files in the build
> >>> directory note the dist_manifest.txt and install_manifest.txt. These will
> >>> be
> >>> present in your build directory.
> >>> Selection_009.png
> >>> <http://gnucash.1415818.n4.nabble.com/file/t375329/Selection_009.png>
> >>>
> >>> David Cousens
> >>>
> >>>
> >>>
> >>> -----
> >>> David Cousens
> >>> --
> >>> Sent from:
> >>> http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html
> >>> _______________________________________________
> >>> gnucash-user mailing list
> >>> gnucash-user@gnucash.org
> >>> 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.
> >>>
> >>
> > _______________________________________________
> > gnucash-user mailing list
> > gnucash-user@gnucash.org
> > 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.
>
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
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.
