Author Topic: [SOLVED - partially] mkrepo script and ~/tmp directory  (Read 469 times)

Offline mikkl

  • Hero Member
  • *****
  • Posts: 872
[SOLVED - partially] mkrepo script and ~/tmp directory
« on: May 01, 2010, 06:14:59 AM »
Since kpackage is no longer supported on KDE4.4 and I sometime install packages from outside the repositories (such as my Brother printer driver), I thought I would create a local repository for managing outside rpms.

Following the directions in this thread, I installed the pkgutils and pkgutils-kde4 packages.

I then created a directory ~/rpm_cache
Using Dolphin, I changed to this directory and opened a terminal window from within Dolphin.  IIRC, the path correctly indicated that I was in the ~/rpm_cache directory

I then ran the mkrepo script but did NOT read closely and typed yes when prompted.  Instead of using ~/rpm_cache as the root directory for setting up the paths, ~/ was used instead and a /src and /tmp directories were created.

This is not what I wanted and further clutters my home directory.

Deleting /src was easy.  Right click-delete and it's gone.

The ~/tmp directory is proving much more difficult to banish.

No matter what I try, when I delete the /tmp directory it is automatically recreated.

I have tried:
-deleting as user from within Dolphin
-deleting as root from within Dolphin
-deteting as root from within Konq

There seems to be a script somewhere that is forcing the existence of this directory.

How do I clean up my machine?

I still would like to have a local repository for rpms that I need to install locally, but at a location of my choosing, not that of this script.

Help cleaning up my install is greatly appreciated!

mikkl
« Last Edit: May 01, 2010, 06:34:12 AM by mikkl »

Offline mikkl

  • Hero Member
  • *****
  • Posts: 872
Re: [SOLVED - partially] mkrepo script and ~/tmp directory
« Reply #1 on: May 01, 2010, 06:36:15 AM »
Doing some testing and exploring, I have determined that the ~/tmp directory is a system directory that exists for every user.  I simply had not noticed it until today; so this part of the mystery is solved.

I am still interested in how to properly set up a local repository (along with recommendations on a location) but that can wait until another day.

mikkl