Getting started with a content filter

[Anteru]

Hi,

> You can look up per-branch configuration options if you want to let
> users control what is stored or where.  But based on the previous
> discussion it seemed to me that you'd probably want to have a file in
> .bzrmeta that gives some additional files that ought to be checked
> out, and the places to put them at?
the main problem is how to distinguish between files with the same path.
I.e. the user might to

bzr add-large foo.png && bzr ci
// mark foo.png as large
bzr rm foo.png && bzr ci
bzr add foo.png && bzr ci
// foo.png is a small file now, and shouldn't be tracked any more

Going with the meta-route, I'm going to check in foo.png.meta when using
add-large, so I have something in the repository to get hold on. How
would this work with .bzrmeta? I definitely need something versioned to
attach the meta-data to, and the first plan is to simply store the
meta-data instead of the actual data in the repository.

Cheers,
  Anteru