Re: removing xchat
Replacing xchat and absorbing the userbase was more-or-less the idea
behind packaging hexchat in the first place, so yes, I'm willing.
It's true you can't directly migrate your configuration, though. Some
settings survive and others do not. I'll chat with upstream about some
kind of a migration script but I don't know how feasible it would
really be.
On Sun, Sep 27, 2015 at 5:01 AM, Sven Hoexter <sven@timegate.de> wrote:
> On Sun, Sep 27, 2015 at 08:48:02AM +0200, Niels Thykier wrote:
>> On 2015-09-27 08:44, Andreas Tille wrote:
>> > On Fri, Sep 25, 2015 at 08:42:18PM +0200, Niels Thykier wrote:
>> >>
>> >> If neither Davide nor Bart (just CC'ed) speak up for keeping it, I am in
>> >> favour of xchat being removed/replaced by hexchat.
>> >
>> > I wonder whether it makes sense to set in hexchat
>> >
>> > Provides: xchat
>> > Replaces: xchat
>> >
>> > to make sure users will not end up with unmaintained software on their
>> > systems.
>>
>> Hi,
>>
>> It would be an excellent idea.
>>
>> However, I suspect you will need a transitional package to actually
>> force the take over (and if not, then it is probably missing a Breaks:
>> xchat as well).
>
>
> Ok so let's add Jesse the hexchat maintainer if he'd be willing to absorb
> the xchat userbase.
>
> As far as I can tell you can't migrate your configure copy&paste
> style, so we kind of force everyone to migrate to a fork and reconfigure.
> Obviously I personally think that's the best way forward but I'm not sure
> if that's the case for everyone. I've always mixed feelings when we force
> something on the user base even if it's with good intentions.
>
> Sven
>
>
Reply to: