[Geany-devel] Geany-Plugins: Adding a maintainer file
Hi folks, What do you think of adding a maintainer file, which basically include only three information: plugin-name, maintainer name, contact email. Cheers, Frank -- http://frank.uvena.de/en/ pgpwvqfqGRnHA.pgp Description: PGP signature ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Geany-Plugins: Adding a maintainer file
Am Samstag, den 17.12.2011, 16:12 +0100 schrieb Frank Lanitz: Hi folks, What do you think of adding a maintainer file, which basically include only three information: plugin-name, maintainer name, contact email. +1 -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
[Geany-devel] plugins.geany.org update - contents now generated from the latest Geany-Plugins release
Hi together, with today's commits [1] the behavior of the gencontent.sh has changed. The script now tries getting the README files from the latest Geany-Plugins release and not from git master anymore. For you as a plugin maintainer, this now means that you'd need to create a branch exactly named as the tag of the latest release and put changes to README files there as well in case they apply for an already released version of Geany-Plugins. gencontent.sh would look for changes in that branch then and not in master. In other words: plugins.geany.org now has the content of the README files of the tag 0.21.1. If you like to improve something there, the changes must be made to a branch called 0.21.1 created from the tag. This should apply to a common work flow when fixing issues in an already released version, so I guess no big deal for anyone of you. Feel free to correct me, if you think I am wrong with this. :) Any further suggestions or improvements are welcome, feel free to fork the stuff and open pull requests. ;) Best Regards, Dominic [1] https://github.com/dmaphy/plugins.geany.org/commits/master -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] plugins.geany.org update - contents now generated from the latest Geany-Plugins release
Am Samstag, den 17.12.2011, 17:05 +0100 schrieb Dominic Hopf: [1] https://github.com/dmaphy/plugins.geany.org/commits/master The repository has moved to the Geany organisation. New link: https://github.com/geany/plugins.geany.org/commits/master Regards, Dominic -- Dominic Hopf http://dominichopf.de/ Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D signature.asc Description: This is a digitally signed message part ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
Re: [Geany-devel] Moving MultiTerm plugin to Geany-Plugins
Hi, I just added the MultiTerm plugin to Geany-Plugins master branch. Please let me know ASAP if it causes you any issues. It still needs to be added to the Waf build system and there's lots of work to do on everything else. Note: there's some build warnings even without make check that are caused by the C code that is generated by valac. There's not much I can do about it, the fixes will come with newer valac versions, I'm sure. Cheers, Matthew Brush On 12/15/2011 08:35 PM, Matthew Brush wrote: Hi, I wanted to move my geany-multiterm[1] plugin into the Geany-Plugins repository and continue development there, but I need help with some things. It's written in Vala[2] using the Geany binding[3] Colomban wrote. My questions are: Is there a maintainer mode or something that can be use to only activate Vala support in Autotools if this plugin is selected to build? Should this go into `build/multiterm.m4`? Should the .c/.h files that valac compiles be checked into the VCS so that people without valac compiler can still compile the plugin? How to make it work with Waf? (Mostly for Colomban) How should the geany.vapi/.deps be distributed? If I make it install into the normal location I guess it will conflict with the official binding, but then again AFAIK the official one isn't really distributed, it just lives in a Gitorious repo[3], so I can't really depend on it (or can I?). Could we move the official Vala binding to Geany-Plugins project as well so that it is released with GP and other plugins can depend on it being there? Cheers, Matthew Brush [1] https://github.com/codebrainz/geany-multiterm [2] https://live.gnome.org/Vala [3] http://gitorious.org/geany-vala-binding ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel ___ Geany-devel mailing list Geany-devel@uvena.de https://lists.uvena.de/cgi-bin/mailman/listinfo/geany-devel
