Login | Register
My pages Projects Community openCollabNet

Discussions > dev > Re: discussion of fsvs setup in common binary packages

fsvs
Discussion topic

Back to topic list

Re: discussion of fsvs setup in common binary packages

Author pmarek
Full name P.Marek
Date 2010-08-31 23:49:30 PDT
Message Hello Gunnar!

>>> But the work begins if files needs to be sorted out because of
>>> privacy or bloating the repo etc. I think fsvs behavior can, because of its
>>> clueness and different use case, be different in that area. Comparing to svn the
>>> fsvs ignore list is also more centric then some sporadic propsets containing
>>> ignore rules.
>>
>>> I am also more for an option that changes the behaviour of "fsvs ignore".
>> "fsvs ignore" is the wrong place - that's for editing the patterns.
>>
>>> What about something like "sync-with-ignore" defaulting to false? Would it be
>>> necessary or even suffice to run a "sync-repos"?
>> As an option which is used on "commit" it's ok.
>
> For files that are already in version control the "fsvs commit" is for sure a
> good place. But what about the files that weren't commited yet und you want to
> get rid from "fsvs st"?
Well, this option should just control what changes are detected for files ...

So, if you look into ops__update_single_entry(), there the full path is already taken
via
    STOPIF( ops__build_path(&fullpath, sts), NULL);

If the option is set, you can just test the patterns and set the entry to FS_REMOVED, if
necessary ...



> My intention is to trigger the add/unversion operations somehow when the ignore
> list is changed via "fsvs ignore load/prepend/append/at=". Where do you think
> the storm breaks loose in the teacup?
The problem is that it's not stored that an entry is removed - that is found (by getting
ENOENT on lstat()) on the next invocation of "status", "commit", or whatever.

So there isn't really a list to change ...
And BTW you'd have to send the "unlink" events to the repository, too. So just removing
from the list of known files isn't enough.


>> I'm sorry, I seem to have caused confusion with my remark about "sync-repos".
>> I meant that there's already a command starting with the letters "sync", and because
>> FSVS accepts abbreviations a new command like "sync-with-ignore" could wreck somebody
>> trying to use "sync-repos".
>> (Although, with one more thought, someone who does "sync-repos" must not care about
>> his
>> WC list anyway.)
>
> Sorry, to mix-up things with that question. I did a quick test for myself now
> and resulting did not care about ignore list changes.
As long as the confusion is resolved ...


Regards,

Phil

--
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!

« Previous message in topic | 8 of 8 | Next message in topic »

Messages

Show all messages in topic

discussion of fsvs setup in common binary packages tekknokra Gunnar Thielebein 2010-07-22 04:05:48 PDT
     Re: discussion of fsvs setup in common binary packages pmarek P.Marek 2010-07-22 08:10:04 PDT
     Re: discussion of fsvs setup in common binary packages tekknokra Gunnar Thielebein 2010-08-31 05:28:43 PDT
         Re: discussion of fsvs setup in common binary packages pmarek P.Marek 2010-08-31 06:45:25 PDT
             Re: discussion of fsvs setup in common binary packages tekknokra Gunnar Thielebein 2010-08-31 07:06:50 PDT
                 Re: discussion of fsvs setup in common binary packages pmarek P.Marek 2010-08-31 08:10:20 PDT
                     Re: discussion of fsvs setup in common binary packages tekknokra Gunnar Thielebein 2010-08-31 09:15:52 PDT
                         Re: discussion of fsvs setup in common binary packages pmarek P.Marek 2010-08-31 23:49:30 PDT
Messages per page: