Topic: Is there a way to list installed contribs?

[Elliott]

I'm having a hard time getting results from a search on this one so I apologize in advance if it's been covered but...

I'm getting ready to migrate 2 SME's into one new one and was hoping to get a list of which contribs are on each. I can tell the obvious ones that have panel additions but I fear that another administrator or myself (long long ago) might have installed something that I don't know about.

I'd like to remove ones that are obsolete or not being used to make the backups cleaner as well. But the basic question here is in the title: Is there a way to list what contribs are installed on 7.x boxes?

Thanks,
E

[byte]

You could use...

rpm -qa --last |head -n 20

Which will list the last 20 lines/installed packages. If you do just...

rpm -qa --last

This will show all rpms.

[Elliott]

You could use...

rpm -qa --last |head -n 20

Which will list the last 20 lines/installed packages. If you do just...

rpm -qa --last

This will show all rpms.

Thanks for the reply. By the looks of the output this is every update as well and I update pretty much every time they're available so this list is chock full of every package on the system.

I guess since there really isn't a set naming convention for contribs this may be harder than I initially thought. I don't suppose there's a full list of what packages would be installed on an unmodified system that I could use  as a DIFF or compare list against my dump?

Or any other suggestions.

-E

[dmay]

The best way I have found is to store all contribs in a single directory. I personally use /root/contribs and store all custom additions (be it rpm or other) here. Makes for quick and easy reference of what contribs are installed on a given server. Also provides a single point to backup/restore from.

Darrell

[Elliott]

The best way I have found is to store all contribs in a single directory. I personally use /root/contribs and store all custom additions (be it rpm or other) here. Makes for quick and easy reference of what contribs are installed on a given server. Also provides a single point to backup/restore from.

Damn that hindsight 

[jdavey]

Darrell,

That's how I have always done it as well.

What about contribs that you install via YUM? Is there a consistent methodology that you have used for YUM installs?

[byte]

What about contribs that you install via YUM? Is there a consistent methodology that you have used for YUM installs?

Just use from command line...

yum localinstall /root/contribs/rpmname.rpm

Thats all.

[byte]

Thanks for the reply. By the looks of the output this is every update as well and I update pretty much every time they're available so this list is chock full of every package on the system.

It does list all yes and sorts in date order.

I guess since there really isn't a set naming convention for contribs this may be harder than I initially thought. I don't suppose there's a full list of what packages would be installed on an unmodified system that I could use  as a DIFF or compare list against my dump?

Most contribs would be ideally be smeserver-contribname.rpm, so you could use grep to grab the smeserver-* contribs.

[byte]

You could also use...

yum list extras

This will list non-standard rpms.

Another which is similar is...

cd /sbin/e-smith/audittools/

./newrpms

[dmay]

What about contribs that you install via YUM?

Yum stores it's downloads in /var/cache/yum. To keep track of contribs, I manaully copy the contrib rpm into /root/contribs. I typically don't worry about dependency rpms as performing the yum install will take care of grabbing these again. However I do add /var/cache/yum into my backup selections just in case I need to perform an offline disaster recovery.

Darrell