Edit Package neochat

A chat client for Matrix, the decentralized communication protocol

https://www.kde.org

Neochat is a client for Matrix, the decentralized communication protocol for instant
messaging.

Refresh
Refresh
Source Files (show merged sources derived from linked package)
Filename Size Changed
neochat-1.2.0.tar.xz 0000244064 238 KB 2 months
neochat-1.2.0.tar.xz.sig 0000000833 833 Bytes 2 months
neochat.changes 0000002503 2.44 KB about 1 month
neochat.keyring 0000003898 3.81 KB 7 months
neochat.spec 0000003397 3.32 KB about 1 month
Comments for neochat 15

Eric Schirra's avatar

ecsos wrote 7 months ago

This package is newer as in n:m:m. And all other matrix clients are in n:m:m. So neochat must in n:m:m also!!



Luca Beltrame's avatar

luca_b wrote 7 months ago

As the KDE team, we'd like to maintain this package. It is developed by KDE and we have familiarity with upstream (and most of us are also KDE contributors).


Fabian Vogt's avatar

Vogtinator wrote 7 months ago

It can be in both, but one of them should be a link to the other. So the .spec files should be merged.


Luca Beltrame's avatar

luca_b wrote 7 months ago

Would that be acceptable if the package here were linked to n:m:m?


Wolfgang Bauer's avatar

wolfi323 wrote 7 months ago

Well, if we (the KDE team) want to maintain it, it should better be the other way round (i.e. the package in n:m:m should link to KDE:Extra) I'd say. ;-)

Personally I don't mind though.


Luca Beltrame's avatar

luca_b wrote 7 months ago

Actually I had it backwards, I meant what you wrote here: that is, link this package to n:m:m. Like this I can also keep a copy in KUE for the usual daily update.


Wolfgang Bauer's avatar

wolfi323 wrote 7 months ago

Ok, my suggestion: submit the package to network:messaging:matrix (minus the .changes file, maybe add an entry on top), and ask them for changing it there to link to KDE:Extra.

The one in network:messaging:matrix doesn't contain the %build_without lang, so isn't suitable for KDE:Unstable:Extra. The rest is mainly cosmetic AFAICS, but I'd prefer the KDE:Extra version...


Luca Beltrame's avatar

luca_b wrote 7 months ago

Do you mean, get their .changes and add ours on top? Or just one like "Adapted for KDE:Extra" or somesuch?


Wolfgang Bauer's avatar

wolfi323 wrote 7 months ago

> Do you mean, get their .changes and add ours on top?
Yes, that's what I'd probably do.

I.e. use their .changes file and add an entry like this:
- Adjust spec file to conform to the KDE team's guidelines

Or something like this.


Wolfgang Bauer's avatar

wolfi323 wrote 7 months ago

That's what I mean: SR#864091

If that gets accepted, we can probably forward it to network:messaging:matrix as-is... (and then ask them to link to KDE:Extra instead)


Luca Beltrame's avatar

luca_b wrote 7 months ago

Accepted. Can you do the honors? ;) If not, I can probably try later this evening.


Wolfgang Bauer's avatar

wolfi323 wrote 7 months ago

SR#864093

I guess it's up to @ecsos now... ;-)


Wolfgang Bauer's avatar

wolfi323 wrote 7 months ago

Ok, now that this is cleared: Do we want to submit it to Factory?


Luca Beltrame's avatar

luca_b wrote 7 months ago

Yes, that was my plan all along. I'll do that this evening along with kquickimageeditor.

openSUSE Build Service is sponsored by