• [gentoo-dev] Can app-office/sc be replaced by app-office/sc-im from GUR

    From Jeff Gazso@21:1/5 to All on Mon Jun 27 05:30:01 2022
    It seems app-office/sc (spreadsheet calculator) was last updated
    upstream about 20 years ago. At this point it's safe to say the
    project is no longer in development.

    There is a currently maintained fork called sc-im (spreadsheet
    calculator - improved) which has been in continuous development for
    about 6 years at this point. It does not exist in the main Gentoo
    repository but app-office/sc-im is present in GURU. The
    app-office/sc-im ebuild appears to be maintained by someone named Dex
    Conner.

    I'm new at this, but it looks to me like the ebuild is in good shape.
    The only thing that jumps out at me is the fact that the package
    manifest needs some TLC.

    My thought is unless some serious deficiency is present in
    app-office/sc-im it should be moved to Gentoo's main ebuild repository
    and the last rites process should be started for app-office/sc. Does
    anyone else have thoughts or comments on this?

    Jeff Gazso

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mike Gilbert@21:1/5 to jeff.gazso@gmail.com on Mon Jun 27 17:00:01 2022
    On Sun, Jun 26, 2022 at 11:24 PM Jeff Gazso <jeff.gazso@gmail.com> wrote:
    My thought is unless some serious deficiency is present in
    app-office/sc-im it should be moved to Gentoo's main ebuild repository
    and the last rites process should be started for app-office/sc. Does
    anyone else have thoughts or comments on this?

    We could probably last rite app-office/sc. It has no maintainer, and a
    couple of open bugs.

    Moving app-office/sc-im to the Gentoo repo is a bit more of an ask.
    Ideally, a Gentoo developer would maintain it. Alternatively, a
    non-developer could maintain it by proxy, but you would need to find a developer to act as proxy or get approval from the Proxy Maintainers
    project. In any case, you should probably reach out to the current
    maintainer in GURU to see what he wants to do.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dex Conner@21:1/5 to Mike Gilbert on Tue Jun 28 01:40:01 2022
    On 22/06/27 10:59AM, Mike Gilbert wrote:
    On Sun, Jun 26, 2022 at 11:24 PM Jeff Gazso <jeff.gazso@gmail.com> wrote:
    My thought is unless some serious deficiency is present in
    app-office/sc-im it should be moved to Gentoo's main ebuild repository
    and the last rites process should be started for app-office/sc. Does
    anyone else have thoughts or comments on this?

    We could probably last rite app-office/sc. It has no maintainer, and a
    couple of open bugs.

    Moving app-office/sc-im to the Gentoo repo is a bit more of an ask.
    Ideally, a Gentoo developer would maintain it. Alternatively, a
    non-developer could maintain it by proxy, but you would need to find a developer to act as proxy or get approval from the Proxy Maintainers
    project. In any case, you should probably reach out to the current
    maintainer in GURU to see what he wants to do.


    I'm the maintainer of app-office/sc-im. Just so everyone is aware, upon talking to Jeff, I've decided to maintain it by proxy. I have some reading
    to do but hopefully I'll have created the necessary pull requests by
    tomorrow.

    I do have just one question: Should I wait until the pull requests are
    merged to remove sc-im from GURU or should I do it after I create the pull requests?

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEE2ISlnG4xsFQ7Mswex1Y9SzFDEmcFAmK6PywACgkQx1Y9SzFD EmcfcA//WK7HLTd4iuQ4utk9UTNmrJWz4FaU7JcdyZbuGw1a7W+1IlYhlKaLrsYQ Bfj13sjZBnrLYPp0m5RHzf4983QgNXBGHSEkId3lfi5pFRJEUK2QCrxk73M3MpHg uyyb3Fc3+FNLaVp3Je3QvF8h//D+aGf3zNDIYOb5wMnZ8Q9Rwm4ws91SjhlVtJ2v jH4iuexJmcYUKuHw8NOwhDQpO1Jpsb+tlLMKZKgkHoTLVb7ethke181wbhx11x5d bpwG6L3jLGRtT3ZmZsN4q/VJ781yN7sB8MY/OylTh3Nz3xxeoz5W7Xzrg1qLtN2Z c8kWYNoEyErUroZ6l+/0hFv5oNJpJ/VDHJBe5b0Qlo8wTX5U7/VprWGgBfDBsXoj o4Y9nk45Wve+qth/9NK/HRvofivoUtNHgRXAMkBUHJGZCw21KbtaHeliaDU+ZDev IeWCPBMxSfu/w5mVFGS5I7tkhIwOVcwDKGsnTlhSPVfDRWdZv1ZOYvomfJ0TCFnt utZzUgKgmLAHSVInHaty89EDLP9NtNyyDd2Z3uF8pclbsGOo2opp2n2tG4QfyLHI 6xOXduk96DmFg86WR60nwdIex4XhC9kXxjjptt40BP9HcUEG/qxwbs0Zfl0EyCP0 K9KRG8uNuNfs8uZpuy2l8DKB0UQZYUdcwAzTw8ucg6VEA4T6R0s=
    =IagL
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrew Ammerlaan@21:1/5 to Dex Conner on Tue Jun 28 06:50:01 2022
    On June 28, 2022 1:37:19 AM GMT+02:00, Dex Conner <cantcuckthis@danwin1210.de> wrote:
    On 22/06/27 10:59AM, Mike Gilbert wrote:
    On Sun, Jun 26, 2022 at 11:24 PM Jeff Gazso <jeff.gazso@gmail.com> wrote:
    My thought is unless some serious deficiency is present in
    app-office/sc-im it should be moved to Gentoo's main ebuild repository
    and the last rites process should be started for app-office/sc. Does
    anyone else have thoughts or comments on this?

    We could probably last rite app-office/sc. It has no maintainer, and a
    couple of open bugs.

    Moving app-office/sc-im to the Gentoo repo is a bit more of an ask.
    Ideally, a Gentoo developer would maintain it. Alternatively, a
    non-developer could maintain it by proxy, but you would need to find a
    developer to act as proxy or get approval from the Proxy Maintainers
    project. In any case, you should probably reach out to the current
    maintainer in GURU to see what he wants to do.


    I'm the maintainer of app-office/sc-im. Just so everyone is aware, upon >talking to Jeff, I've decided to maintain it by proxy. I have some reading >to do but hopefully I'll have created the necessary pull requests by >tomorrow.

    I do have just one question: Should I wait until the pull requests are >merged to remove sc-im from GURU or should I do it after I create the pull >requests?

    Please remove it only after merging, this creates a seemless transition for the users of this package.

    Best regards
    Andrew

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)