| 1 |
On 02/12/2010 01:38 PM, Brian Harring wrote: |
| 2 |
> On Fri, Feb 12, 2010 at 12:54:21PM -0800, Zac Medico wrote: |
| 3 |
>> Hi, |
| 4 |
>> |
| 5 |
>> I'm thinking about adding a UUID file in /var/db/pkg, for comparing |
| 6 |
>> installed packages to binary packages. We already have BINPKGMD5, |
| 7 |
>> but the problem with that is that the MD5 of a binary package |
| 8 |
>> changes when it's updated for package moves. A UUID would be |
| 9 |
>> assigned at build time and remain constant thereafter. We can use |
| 10 |
>> python's uuid.uuid4() function to generate a random UUID. Any |
| 11 |
>> suggestions for alternative approaches? |
| 12 |
> |
| 13 |
> Purpose? |
| 14 |
> ~harring |
| 15 |
|
| 16 |
If you build binary packages for installation on multiple systems, |
| 17 |
and periodically have to rebuild packages for various reasons |
| 18 |
(revdep-rebuild or whatnot), it makes it easier to know whether a |
| 19 |
particular system has the latest build installed. Then you can |
| 20 |
create a package set that reinstalls any installed packages that are |
| 21 |
not the latest build. |
| 22 |
|
| 23 |
It's basically a catch-all for rebuilds that aren't tracked by other |
| 24 |
kinds of metadata yet. Eventually, we should introduce metadata to |
| 25 |
indicate when things need to be reinstalled, as discussed in this bug: |
| 26 |
|
| 27 |
https://bugs.gentoo.org/show_bug.cgi?id=192319 |
| 28 |
|
| 29 |
In the mean time, it's nice to have a catch-all for keeping systems |
| 30 |
synchronized with the latest builds. We may want to consider |
| 31 |
including it in the $PKGDIR/Packages file as a convenience for |
| 32 |
binhost users. |
| 33 |
-- |
| 34 |
Thanks, |
| 35 |
Zac |
Archives