|
2010-02-02
, 09:01
|
Posts: 3,617 |
Thanked: 2,412 times |
Joined on Nov 2009
@ Cambridge, UK
|
#2
|
|
2010-03-03
, 12:09
|
Posts: 38 |
Thanked: 17 times |
Joined on Jun 2008
|
#3
|
|
2010-03-03
, 12:16
|
Posts: 3,617 |
Thanked: 2,412 times |
Joined on Nov 2009
@ Cambridge, UK
|
#4
|
|
2010-03-03
, 13:41
|
Posts: 113 |
Thanked: 44 times |
Joined on Feb 2010
|
#5
|
|
2010-03-03
, 14:04
|
Posts: 3,617 |
Thanked: 2,412 times |
Joined on Nov 2009
@ Cambridge, UK
|
#6
|
|
2010-03-03
, 14:27
|
Posts: 113 |
Thanked: 26 times |
Joined on Feb 2010
@ Port of Spain, Trinidad & Tobago
|
#7
|
|
2010-03-03
, 14:30
|
Posts: 3,617 |
Thanked: 2,412 times |
Joined on Nov 2009
@ Cambridge, UK
|
#8
|
|
2010-03-03
, 16:09
|
Posts: 3,617 |
Thanked: 2,412 times |
Joined on Nov 2009
@ Cambridge, UK
|
#9
|
I'll look at knocking up a command-line script to do this then. Should be fairly straightforward.
perl package_sources.pl
perl package_sources.pl Ovi
The Following 9 Users Say Thank You to Rob1n For This Useful Post: | ||
|
2010-03-03
, 17:58
|
Posts: 113 |
Thanked: 44 times |
Joined on Feb 2010
|
#10
|
Is there an easy way of figuring out which packages I have installed from a specific repository, say extras-testing?
I thought of getting a list of packages from that repository and checking against dkpg -l, but is there a simpler way?
Edit: the reason for this is to start removing extras-devel and -testing stuff one by one until I see what causes the degraded performance I see occaionally.
Last edited by nex; 2010-02-01 at 22:52.