Skip to content

Weed out the inkscape zoo a bit #173

Closed
thomas opened this issue Nov 5, 2021 · 3 comments
Closed

Weed out the inkscape zoo a bit #173

thomas opened this issue Nov 5, 2021 · 3 comments

Comments

@thomas
Copy link
Contributor

thomas commented Nov 5, 2021

Right now we have 10 inkscape packages:

 1  inkscape-0.92.1-0
 2  inkscape-0.92.2-0
 3  inkscape-0.92.3-0
 4  inkscape-0.92.4-0
 5  inkscape-0.92.4-1
 6  inkscape-0.92.4-2
 7  inkscape-1.0-0
 8  inkscape-1.0-1
 9  inkscape-1.0beta0-0
10  inkscape-1.1.1-0

Registered via /usr/local/package and (probably) in use are:

 4  inkscape-0.92.4-0
 8  inkscape-1.0-1
10  inkscape-1.1.1-0

Dump/archive the rest, or create an 'attic' ?

@donald
Copy link
Contributor

donald commented Nov 5, 2021

Yes, we need to find a way to get rid of unused obsolete packages. We can't really monitor the usage, though, so that we have to guess, try and see. For that it would be nice if the package could be restored quickly. Moving them into some "/package/pkg/attic" would produce extra backup load. Maybe make "attic" a symlink to some /scratch/local on ex to avoid that?

@thomas
Copy link
Contributor Author

thomas commented Nov 5, 2021

Proposal after discussion:

Comment out the unwanted package in /project/config/src/mxpkg and append the date (s.b.).

After some time the package gets archived on tape. No attic, no stashing in /scratch/local .

<<< inkscape-1.0beta0-0
>>> # inkscape-1.0beta0-0 # Fri Nov  5 10:17:14 CET 2021

@wwwutz
Copy link
Contributor

wwwutz commented Nov 5, 2021

ACK

@thomas thomas closed this as completed Nov 5, 2021
Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants