Hi Hannes and Lova,

Thanks for asking and answering. We will proceed as recommended. It might be worth adding a relevant section in the plugins developer documentation or cookbook.

To follow up about the naming convention, as written in https://github.com/qgis/QGIS-Django/issues/475 I would suggest to make sure that new plugins folders are Python compliant since a plugin is a Python package and may be imported by other "Python things" within QGIS.

Regards,
Julien

Le 14/10/2024 à 14:43, Lova Andriarimalala via QGIS-Developer a écrit :
Dear Hannes,

Sure, I think that's a great idea.
I think it's better to rename the old plugin first if you want to keep the same name for the new one, as uploading a new plugin with an existing name is not allowed. Please, feel free to let me know if you need help with this. It's also possible to update the name from the metadata, although this option is disabled by default.

Best regards,

Lova Andriarimalala
*QGIS Full Stack Developer

*
*T *: +27(0) 87 809 2702 *E *:**l...@kartoza.com *W* : kartoza.com <http://kartoza.com>



/This email and any attachments are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you / /have received this email in error, please notify the sender immediately and delete it from your system. Unauthorised use, disclosure, or copying/
/of the contents is prohibited./


On Mon, 14 Oct 2024 at 14:34, Johannes Kröger (WhereGroup) <johannes.kroe...@wheregroup.com> wrote:

    Hi Lova,

    thanks for your swift response!

    That's what I expected and what seems very reasonable, considering
    the potential for problems. I think we will simply publish a new
    version of the old plugin to display a message to our (few)
    existing users and create a "new" plugin for the new version.

    That should keep surprise factor low and allow a clean cut without
    any unforeseen issues.

    Are we able to upload a new plugin that uses the same name as the
    existing, deprecated one? Or do we have to choose a new name (or a
    different name for the old one) first?

    Thank you!

    Cheers, Hannes

    On 11.10.24 15:21, Lova Andriarimalala wrote:
    Dear Hannes,

    At the moment, it's not possible to change a plugin's directory
    name (package_name) even through the administration page.

    This feature was previously requested with a PR, but it was
    closed due to potential client-side issues. When the package_name
    changes, QGIS may recognize the plugin as a new one, leading to
    possible installation errors.
    You can find the related PR and a more detailed discussion about
    it at https://github.com/qgis/QGIS-Django/pull/271.

    However, we are open to new ideas and suggestions on this matter.
    I can also re-check the feature to have an updated detail about it.

    Best regards,

    Lova Andriarimalala
    *QGIS Full Stack Developer

    *
    *T *: +27(0) 87 809 2702 *E *:**l...@kartoza.com *W* :
    kartoza.com <http://kartoza.com>



    /This email and any attachments are confidential and intended
    solely for the use of the individual or entity to whom they are
    addressed. If you /
    /have received this email in error, please notify the sender
    immediately and delete it from your system. Unauthorised use,
    disclosure, or copying/
    /of the contents is prohibited./


    On Fri, 11 Oct 2024 at 14:30, Johannes Kröger (WhereGroup) via
    QGIS-Developer <qgis-developer@lists.osgeo.org> wrote:

        Hi there!

        Wonderful people from Oslandia have started collaborating on our
        experimental (and somewhat buggy) Profile Manager plugin.

        https://plugins.qgis.org/plugins/profile-manager/
        https://github.com/WhereGroup/profile-manager/

        One of the changes was restructuring the repository and using a
        PEP8-compliant directory name for the plugin's module directory
        ("profile_manager" instead of "profile-manager").

        Now the automated CI/CD upload of new releases fails.
        Presumably because
        the site expects "profile_manager".
        
https://github.com/WhereGroup/profile-manager/issues/10#issuecomment-2402479699

        Would it be possible to update that on the plugin's existing
        Plugins
        repository entry?

        I saw
        https://lists.osgeo.org/pipermail/qgis-developer/2024-May/066744.html

        but that was only for the user visible name, the plugin's URL
        and the
        installed directory name stayed the same.

        What would it mean for existing users?
        Would they simply not be notified about new releases, and
        have to
        install the "new" plugin manually?
        Or would something break and require manual intervention,
        e.g. two
        version of the plugin being installed and loaded, one in
        plugins/profile_manager and the old one in
        plugins/profile-manager?

        Cheers, Hannes

-- Johannes Kröger / GIS-Entwickler/-Berater

        ***********************************************************
        Schon gewusst?
        In unserem Blog geben wir Tipps & Tricks zu
        Open-Source-GIS-Software
        und berichten aus laufenden und abgeschlossenen Projekten
        https://wheregroup.com/blog/
        ***********************************************************

        WhereGroup GmbH
        c/o KK03 GmbH
        Lange Reihe 29
        20099 Hamburg
        Germany

        Tel: +49 (0)228 / 90 90 38 - 36
        Fax: +49 (0)228 / 90 90 38 - 11

        johannes.kroe...@wheregroup.com
        www.wheregroup.com <http://www.wheregroup.com>

        Geschäftsführer:
        Olaf Knopp, Peter Stamm
        Amtsgericht Bonn, HRB 9885
        -------------------------------


        _______________________________________________
        QGIS-Developer mailing list
        QGIS-Developer@lists.osgeo.org
        List info:
        https://lists.osgeo.org/mailman/listinfo/qgis-developer
        Unsubscribe:
        https://lists.osgeo.org/mailman/listinfo/qgis-developer

-- Johannes Kröger / GIS-Entwickler/-Berater

    ***********************************************************
    Schon gewusst?
    In unserem Blog geben wir Tipps & Tricks zu Open-Source-GIS-Software
    und berichten aus laufenden und abgeschlossenen Projekten
    https://wheregroup.com/blog/
    ***********************************************************

    WhereGroup GmbH
    c/o KK03 GmbH
    Lange Reihe 29
    20099 Hamburg
    Germany

    Tel: +49 (0)228 / 90 90 38 - 36
    Fax: +49 (0)228 / 90 90 38 - 11

    johannes.kroe...@wheregroup.com
    www.wheregroup.com <http://www.wheregroup.com>

    Geschäftsführer:
    Olaf Knopp, Peter Stamm
    Amtsgericht Bonn, HRB 9885
    -------------------------------


_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info:https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe:https://lists.osgeo.org/mailman/listinfo/qgis-developer
--
Oslandia <https://oslandia.com/?utm_source=email&utm_campaign=signature_oslandia&utm_medium=email>- Geotribu <https://geotribu.fr/?utm_source=email&utm_campaign=signature_oslandia&utm_medium=email>

Attachment: OpenPGP_0x5375CD81333F311E.asc
Description: OpenPGP public key

BEGIN:VCARD
VERSION:4.0
N:Moura;Julien;;;
FN:Julien Moura (Oslandia)
NICKNAME:jmoura
EMAIL;PREF=1;TYPE=work:julien.mo...@oslandia.com
EMAIL:juli...@oslandia.com
TZ:Europe/Paris
URL;TYPE=work:https://oslandia.com/
URL:https://geotribu.fr/
ORG:Oslandia
END:VCARD

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

_______________________________________________
QGIS-Developer mailing list
QGIS-Developer@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer

Reply via email to