[TYPO3-dev] ExtManager: ignoring files in CVS and .svn subdirectories of an extension

Dimitri Tarassenko mitka at mitka.us
Thu Mar 16 21:44:15 CET 2006


Martin,

On 3/16/06, Martin Kutschker <Martin.Kutschker at n0spam-blackbox.net> wrote:

> IMHO ext mgm should ignore all files starting with a dot. And I see no
> reason why I want to ship .htaccess in the extension itself. If the admin
> needs one he should create one. On windows it would be fine if the ext. mgm
> could detect the hidden flag, but I'm not sure if there is a PHP api for this.
>
> But having a flag that adds file names to the ignore list is fine. But why
> on an extension level? I'd think that one list for an installation should
> be enough.

Not really - if you have this list on an extension level it gets
checked in the CVS/svn together with the extension it is describing.
This way if you ever move an extension from an installation to an
installation you keep this info.

Also, just having .* files ignored does not solve the problem fully -
depending on the IDE/editor you use for extension development, there
could be bunch of ~bak files, project files like .project and *.kpf,
line mark files (jEdit) etc.

Also, I've been thinking about the problem Karsten described, and it
looks like there need to be 2 lists:

a) files/directories ignored by EM "comliance" checker, but that are
exported by the EM to a file/TER and tracked by checksums (folders for
internal scripts/libraries)

b) files/directories ignored by EM completely (CVS/SVN, project files
and other files created by IDE).

--
Dimitri Tarassenko


More information about the TYPO3-dev mailing list