[csw-maintainers] php5 packaging

[Ben Walton]

Excerpts from Peter FELECAN's message of Tue May 05 14:09:07 -0400 2009:
> Using transition packages? A transition package serves as a temporary
> package, offering 1:1 content, having the same name as the one
> transitioned. Of course, after the transition, the package disappears or
> has a lesser surface.

So have an empty package named php5 that depends on php5core,
php5session, etc?  Then stop updating php5 at some point in the
future?  That works, but leaves the dangling (although harmless) php5
empty package.  Is there a way to handle it other than this?

I like the extra granularity that Mike introduced, but if users break
their setups (or waste time sorting it out, anyway), they may not be
very happy.

Thanks
-Ben
-- 
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20090505/5e9c5f66/attachment-0001.asc>