Hi, all!
So i'm now running geany from svn instead of a package repo, and now i'm curious if there is a pattern/trick/best practice for collecting various plugins and keeping them up to date vis-a-vis my compiled geany. The goal here is to reduce the number of directories in which i have to type (svn up && make &&make install).
What do you long-time geany/plugin developers do to keep everything in sync?
Am 01.07.2011 10:56, schrieb Stephan Beal:
So i'm now running geany from svn instead of a package repo, and now i'm curious if there is a pattern/trick/best practice for collecting various plugins and keeping them up to date vis-a-vis my compiled geany. The goal here is to reduce the number of directories in which i have to type (svn up && make &&make install).
What do you long-time geany/plugin developers do to keep everything in sync?
I do have a script winch is catching all archives from git and svn. As plugin API is not changing this often I don't need to recompile all plugins so I'm doing only the once which I'm using on a more regular basis ... and most of them are inside the geany-plugings repository also.
I was thinking to build also a global make script but failed due lag of motivation :D
Cheers, Frank
On Fri, Jul 1, 2011 at 1:45 PM, Frank Lanitz frank@frank.uvena.de wrote:
I was thinking to build also a global make script but failed due lag of motivation :D
That's what i'm talking about :).
Would you mind posting your script or sending it off-list? If you got started with the makefile, send it, too - i'm "not too bad" with make and might be able to complete it for you.
Am 01.07.2011 14:04, schrieb Stephan Beal:
On Fri, Jul 1, 2011 at 1:45 PM, Frank Lanitz <frank@frank.uvena.de mailto:frank@frank.uvena.de> wrote:
I was thinking to build also a global make script but failed due lag of motivation :DThat's what i'm talking about :).
Would you mind posting your script or sending it off-list? If you got started with the makefile, send it, too - i'm "not too bad" with make and might be able to complete it for you.
Well, it was a shell script like
for i in git/*; do make all install fi
But I guess I already deleted it again. Will have a look later.
Cheers, Frank
On Fri, Jul 1, 2011 at 2:31 PM, Frank Lanitz frank@frank.uvena.de wrote:
for i in git/*; do make all install fi
But I guess I already deleted it again. Will have a look later.
If it was that simple then please don't trouble yourself - i think i can manage to recreate that ;).
Do you happen to have a list of the svn repos for the plugins you install? i'm mostly interested in VC and tree browser, but i think the tree browser comes with geany.
Am 01.07.2011 14:53, schrieb Stephan Beal:
Do you happen to have a list of the svn repos for the plugins you install? i'm mostly interested in VC and tree browser, but i think the tree browser comes with geany.
I install all plugins by default I've checked out and build dependencies are fetching, but not all are turned on.
So my plugin dialog looks a bit like http://frank.uvena.de/tmp/plugins.png (screenshot is well.. quiet old, but nothing much changed :) )
Cheers, Frank
Cheers, Frank
On Fri, Jul 1, 2011 at 3:06 PM, Frank Lanitz frank@frank.uvena.de wrote:
http://frank.uvena.de/tmp/plugins.png (screenshot is well.. quiet old, but nothing much changed :) )
Ach du lieber - davon moechte ich nur VC und TreeBrowser haben :).
So that seems to imply that i can just check out the top-level geany-plugins tree and work from there. Good - i was afraid i was going to have to collect plugins for N repos.
Vielen Dank!
Am 01.07.2011 15:09, schrieb Stephan Beal:
So that seems to imply that i can just check out the top-level geany-plugins tree and work from there. Good - i was afraid i was going to have to collect plugins for N repos.
Well, most of the plugins are really inside geany-plugins-repo inside geany-plugins folder with a common build system. A few more plugins you will catch from other places.
Cheers, Frank