[csw-maintainers] Restart: cvsproxy release

[Dagobert Michelsen]

Hi,

there hasn't been much progress on this topic, so I'll grab out my old  
mail:

Am 10.11.2009 um 20:37 schrieb Dagobert Michelsen:
> Am 10.11.2009 um 20:28 schrieb Peter Bonivart:
>> On Tue, Nov 10, 2009 at 8:22 PM, Dagobert Michelsen  
>> <dam at opencsw.org> wrote:
>>> I noticed cvsproxy is still in testing/. Is it ready for release?
>>
>> James complained about an old bug with the current release. If people
>> upgrade the remove procedure of the old package may screw up
>> inetd.conf and James wants my package to make sure this doesn't
>> happen.
>
> Just looked. I guess it is time now for the package hooks. We need
> a global directory with script to fix messed-up stuff like package
> renames and this kind. In this case it should be some kind of
>  on-upgrade-start:
>    if( package eq "CSWcvsproxy" && version eq "1.0.1" ) then
>      if( readlink( /etc/inetd.conf ) eq "./inet/inetd.conf" ) then
>        touch /var/run/CSWcvsproxy-redo-link
>
>  on-upgrade-end:
>    if( package eq "CSWcvsproxy" && version eq "1.0.1" ) then
>      if( -f /var/run/CSWcvsproxy-redo-link )
>        rm -f /etc/inetd.conf
>        ln -s ./inet/inetd.conf /etc/inetd.conf
>
> Hey, you did implement package hooks only days away, so this should  
> be really
> easy. What is left is a concept on how to bundle and distribute these
> fix-hooks. On each upgrade they must be updated first.

Now, any feedback on this? I want cvsproxy released soon.


Best regards

   -- Dago