[Vm-dev] Re: why are plugins.int and plugins.ext in .gitignore?

[Tobias Pape]

Hi,

Something's amiss here.
Because the .gitignore explicitly "unignores" them:

...
# Don't track build directories.
/build*/**/*
# except do track these files
#...
!mkNamedPrims.sh
!mvm
!NotYetImplemented
!plugins.ext
!plugins.int
!Squeak.def.in
#...

Do you have changed yours?

Best regards
	-Tobias


On 07.09.2016, at 10:04, Eliot Miranda <eliot.miranda at gmail.com> wrote:

> and the same goes for mvm...
> 
> McStalker.oscogvm$ git add build.macos32x86/pharo.stack.spur/mvm
> The following paths are ignored by one of your .gitignore files:
> build.macos32x86/pharo.stack.spur/mvm
> Use -f if you really want to add them.
> fatal: no files added
> 
> Why are essential files being included in .gitignore?
> 
> On Wed, Sep 7, 2016 at 10:03 AM, Eliot Miranda <eliot.miranda at gmail.com> wrote:
> McStalker.oscogvm$ git add build.macos32x86/pharo.stack.spur/*
> The following paths are ignored by one of your .gitignore files:
> build.macos32x86/pharo.stack.spur/Makefile
> build.macos32x86/pharo.stack.spur/plugins.ext
> build.macos32x86/pharo.stack.spur/plugins.int
> Use -f if you really want to add them.
> fatal: no files added
> McStalker.oscogvm$ vi .gitignore 
> McStalker.oscogvm$ git add -f build.macos32x86/pharo.stack.spur/*
> 
> plugins.int and plugins.ext are important; they specify the set of plains to be built.  They should not be in .gitignore.  Why are they there?
> _,,,^..^,,,_
> best, Eliot
> 
> 
> 
> -- 
> _,,,^..^,,,_
> best, Eliot