[wpkg-users] Package Renaming [SEC=UNCLASSIFIED]

[Leon Hedding (ICT)]

What you describe is exactly what I am thinking. The other bit is as you
say, it is quite difficult to read logs since the GUID would be in the
logs then. That is why I am wondering if having an actual (optional)
GUID value would be of benefit. It might be over kill, but would
certainly help in at least the run once instance.

Cheers,

Leon Hedding


-----Original Message-----
From: Rainer Meier [mailto:r.meier at wpkg.org] 
Sent: 20 May 2008 09:37
To: Leon Hedding (ICT)
Cc: wpkg
Subject: Re: [wpkg-users] Package Renaming [SEC=UNCLASSIFIED]

To make it clear again. WPKG uses two attributes within the package 
which can be used:
id:
This attribute is the unique identifier of each package. It cannot be 
changed/renamed without making WPKG think it is a different package. So 
if you put the GUID there it's fine - as long as you don't change the
GUID.

name:
More descriptive name - you can put any string in here. You might also 
change this name later on without affecting WPKG at all.

So to take our Pidgin example again you could create a package like

<packages>
      <package
	id="{unique-GUID}"
	name="Gaim"
	revision="1"
	reboot="false"
	priority="100">

...

      </package>
</packages>

After the release of Pidgin you can do the following:

<packages>
      <package
	id="{unique-GUID}"
	name="Pidgin"
	revision="2"
	reboot="false"
	priority="100">

...

      </package>
</packages>


This would upgrade the Gaim Package to Pidgin. As long as you do not 
change the GUID within the "id" field.

I am not fully sure if this is what you meant. So please don't shoot me 
if not. I am sure you could explain it to me if this did not match your 
expectations.


br,
Rainer