• Back to Project

Comments for UnusedPkg

I'm sorry but this project is completly useless, if you use an automated update tool. Indicated is, when the project was last updated - not run.

Re: criteria

> Hi,

>

> How do you determine the "idle

> time" of a package? I don't quite

> understand the times it comes up with on

> my Slack12 installation - things I

> haven't touched in weeks are being

> listed as 1 day ago, for example.

>

>

> Cheers,

> Tink

Then, UnusedPkg checks the "access time" (verifiable with ls -alu filename or stat -c %x filename). As said, this timestamp is update by any file data request, like ldconfig library check. I hope it can be useful and thank you for downloading UnusedPkg =)

Re: criteria

> Hi,
>
> How do you determine the "idle
> time" of a package? I don't quite
> understand the times it comes up with on
> my Slack12 installation - things I
> haven't touched in weeks are being
> listed as 1 day ago, for example.

> Cheers,
> Tink

And answering my own question: if ldconfig got run a
package with files in a path in /etc/ld.so.conf will be

flagged "active".

criteria
Hi,

How do you determine the "idle time" of a package? I don't quite understand the times it comes up with on my Slack12 installation - things I haven't touched in weeks are being listed as 1 day ago, for example.

Cheers,

Tink