reproduce-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[task #16270] Uninstall method for python + python modules


From: Boud Roukema
Subject: [task #16270] Uninstall method for python + python modules
Date: Tue, 4 Oct 2022 12:49:18 -0400 (EDT)

URL:
  <https://savannah.nongnu.org/task/?16270>

                 Summary: Uninstall method for python + python modules
                 Project: Maneage
               Submitter: boud
               Submitted: Tue 04 Oct 2022 04:49:17 PM UTC
         Should Start On: Tue 04 Oct 2022 12:00:00 AM UTC
   Should be Finished on: Tue 04 Oct 2022 12:00:00 AM UTC
                Category: Software
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
        Percent Complete: 0%
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                  Effort: 0.00


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Tue 04 Oct 2022 04:49:17 PM UTC By: Boud Roukema <boud>
When debugging or testing improvements to the python build system (python.mk)
in Maneage, it would be good to have a clean method for uninstalling _all_
python libraries and binaries and python module libraries and binaries.

My best recent attempt was

rm -fv .local/version-info/python/; rm -fv .local/bin/python; rm -fr
.local/lib/python*; rm -fr .build/.cache/Python-Eggs/; rm -fv
.local/version-info/proglib/python-3.10.6; rm -fv .local/bin/cy*; rm -fv
.local/version-info/proglib/cy*; rm -fvr .local/include/python3.10* ; rm -fv
.local/bin/f2py*

but on doing './project configure --existing-conf' I still got fatal errors of
the style

FileExistsError: File already exists: ...


The only practical method I found of uninstalling python, in order to get a
clean test of an update to python, was to remove the whole '.build/' tree. 
(In principle, removing '.build/software/' should be enough.)

(In Debian, _aptitude purge PACKAGE_ removes all traces of the package,
including any configure files installed with PACKAGE and subsequently modified
by the sysadmin. An alternative is _aptitude remove PACKAGE_ , which does not
remove configuration files.)








    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/task/?16270>

_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]