Re: Repo information inside rpm?

Hi,

On Fri, Aug 13, 2004 at 01:03:53PM -0500, Rex Dieter wrote:
> I, for one, rarely rebuild packages on stability/component changes, 
> particularly when moving from testing->stable.  I wouldn't be 
> comfortable being forced to rebuild for this.
> 
> Now, if it were possible to modify tags of existing rpms...

On Fri, Aug 13, 2004 at 12:11:24PM -0700, Fernando Pablo Lopez-Lezcano wrote:
> Having the location of the package _in_ the package is a problem in the
> sense that the package is no longer "relocatable" without rebuilding
> (unless, as was mentioned in the thread, there is a tool that enables
> you to change the headers of an already built package). And if a change
> in url is needed, then all packages suddently contain stale information.
> That is very bad.  

I have written a tool that modifies release tag entries (so that
foo-1.2.3-4.src.rpm can effectively generate
foo-1.2.3-4.rhfc2.i386.rpm). You need to resign the modified package,
of course, but header manipulation is possible.

OTOH I would stringly advise against it, as it will nevertheless
generate confusion (same package, different timestamps and md5sums).

So it would be better to not encode semi-volatile meta-data into the
package. How about a meta-specfile, where this and other information
(like the canonical URL) is kept?
-- 
Axel.Thimm at ATrpms.net

_______________________________________________
repo-coord mailing list
[email protected]
http://lists.atrpms.net/mailman/listinfo/repo-coord

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBHT5UQBVS1GOamfERApGRAKCG5ppaBXBb+BNp/36abyQao3ehIACeLJn0
JB0uftHR5F4wxWi3pJqe68U=
=PKPK
-----END PGP SIGNATURE-----