[Vm-dev] script to add internal plugins ?

[Sophie Kaleba]

Hi Tim,

I hadn't thought about that, thanks ! I will make sure not to create any
duplicate of these plugins

I knew indeed that I could edit all the plugins.*files by hand, that was
the reason why I was looking for a script. Please forgive my laziness :-)

Sophie


2017-05-10 20:02 GMT+02:00 tim Rowledge <tim at rowledge.org>:

>
>
> > On 10-05-2017, at 10:47 AM, Sophie Kaleba <sophie.kaleba at gmail.com>
> wrote:
> >
> > Hi again
> >
> > I want to modify the plugins.int files to add some internal plugins to
> the different pharo distributions (http://forum.world.st/
> Missing-plugins-to-make-the-vmProfiler-work-on-Pharo-td4946444.html).
>
> It’s just a text file so you edit with your favourite text editing tools
> (smalltalk, obviously!) and add another line with the name of your plugin.
>
> If the plugin is already listed in the *other* plugins.* file then you’d
> want to remove it as well - ie to change FooPlugin from being built
> internal to external, delete it from plugins.int and add to plugins.ext
>
> You could very simply try this out by moving pretty much any current
> plugin from one list to another and running a build, just to convince
> yourself it works ok. You might also take a look though the assorted
> plugins.* files in the many `build.*/build*` directories to see a lot of
> examples. And indeed a lot of cases where a plugin appears to be
> near-randlomly included or not, something that could do with tidying up.
> And if you were to conclude that making things tidier and doing test builds
> was a project worth spending a little time on then you would certainly earn
> my thanks...
>
>
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Fractured Idiom:- LE ROI EST MORT. JIVE LE ROI - The King is dead.  No
> kidding.
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20170510/20a6ff34/attachment.html>