Login | Register
My pages Projects Community openCollabNet

Discussions > dev > Re: Getting INSTALLED to work

Project highlights: Stable Version: 1.6.1, Development Version: 1.7.6

Discussion topic

2020-04-07: This site is going to be decommissioned and shut down on 2020-07-01. Please copy and archive any data you wish to keep before that date.

Back to topic list

Re: Getting INSTALLED to work


Author theslack
Full name Jack Neely
Date 2006-08-25 13:46:15 PDT
Message This has been committed. Sorry I've been a bit slow, between work and
my volunteered hacking that must be done for Fedora Core 6...

On 8/19/06, Pauline Middelink <middelink at polyware dot nl> wrote:
> LS,
> Well, the previous release has not yet time to cool down, or here is
> Pauline with a new set :)
> In it you will find the following issues attacked.
> 1. CurrentDB._findNewest() changed so it wont need to iterate over
> each name, instead get the rpm_id in the first pass and use that
> later to build a list of active rpm_id's.
> 2. Added info field to INSTALLED. It can have 5 values:
> 0 - OLDIE: rpm for which a newer version is also installed (e.g. kernel)
> 1 - UP2DATE: rpm which is as recent as we have
> 2 - WEIRD: installed rpm which is MORE RECENT than we have!?!
> 3 - UPDATABLE: rpm for which we have a newer version
> 4 - ORPHANED: rpm of which we dont know anything.
> 3. Added _updateInstalledPackages and call that from all functions which
> change either the accessable RPMs (scan_dir,subscribe,​unsubscribe)
> or the installed RPMS (add/remove packages)
> 4. Changed function parameters for profile.add/remove packages. This
> way the db function can process the list in one go and calculate
> the changes for 'info'.
> PS, I'm not overly fond of the field name 'info', suggestions welcome.

Yeah, neither am I. I'll sit down and look at this closer a soon.

> PPS. I'm finaly able to have a little PHP page tell me which registered
> systems are out-of-date! No more joins all over the place, just by
> looking at the INSTALLED table. Color me happy :) Yeah!

If folks out there are interested in hacking on the TurboGears web
frontend... :-)

> PPPS. Not sure what to do about the package_id in INSTALLED. I'm not really
> using it, and dont see a posible use for it in the near future. Kill
> it?
> PPPPS. The website in current wont work for me. The framework needs python24
> which is not in my distro. I did however patch a bug in MySQLdb
> module, so it can co-exist with PHP in the same server. (the rpm
> is hardcoded to use mysqlclient10, and php-mysql uses libmysqlclient14,
> an accident waiting happen!)

Red Hat hasn't fixed that yet? Geez....


> PPPPPS. Note to self, must stop PPS'ing... :)
> Met vriendelijke groet,
> Pauline Middelink
> --
> GPG Key fingerprint = 2D5B 87A7 DDA6 0378 5DEA BD3B 9A50 B416 E2D0 C3C2
> For more details look at my website http://www.polyware.​nl/~middelink

« Previous message in topic | 2 of 2 | Next message in topic »


Show all messages in topic

Getting INSTALLED to work Pauline Middelink <middelink at polyware dot nl> Pauline Middelink <middelink at polyware dot nl> 2006-08-19 11:51:01 PDT
     Re: Getting INSTALLED to work theslack Jack Neely 2006-08-25 13:46:15 PDT
Messages per page: