logo       
Google Custom Search
    AddThis Social Bookmark Button
-->

Re: Re: [1.0.1] darcs dist and tar: msg#00337

Subject: Re: Re: [1.0.1] darcs dist and tar
On Fri, Jan 28, 2005 at 08:20:31PM +0100, Juliusz Chroboczek wrote:
> >> Hmm...  Darcs export?  Or do you have any better suggestions?
> 
> > darcs list?  darcs manifest?  darcs controlled?
> 
> Hold on...  I think there's a misunderstanding.
> 
> I'm speaking of creating the directory that darcs would create when
> doing darcs dist just before running the predist hook and tar.  In
> other words, creating a pristine tree.
> 
> This can currently be done by hand by doing
> 
>   cp -r _darcs/current ../foo

Perhaps this could be an option to "dist", since it really (as you said)
does the same thing, except without the tarring and gzipping.  And it could
even "benefit" from the "predist" option, just as a 

> You're speaking of listing the managed files, which can be done by
> with
> 
>   find _darcs/current | sed 's|^_darcs/current/|//'
> 
> I'm glad to add either command (or even both), just let me know which
> is useful.

Naming-wise I'd like a "manifest" command, which would also be useful
in... I've forgotten what.  Prefferably with a null-delimited option so we
could handle filenames with embedded newlines and spaces.

Ideally, I'd like the manifest command to be a subcommand of a new "query"
command.  I'd like to move towards putting all the "query" commands
together in that way.  This would require a bit of infrastructure, but it's
infrastructure I'd like to have, which I also might like to use for
optimize.  Most of the options to optimize really aren't modifications on a
particular action, but rather are separate actions.

darcs optimize <relink|compress|uncompress>

makes more sense to me than

darcs optimize --relink --uncompress etc.

The constraint would be that we couldn't optimize several things at once,
and we couldn't stick these things into defaults so we would be able to run
a single "optimize" to fix everything about the repository.

So maybe optimize isn't a great place for subcommands, but for query it
is, since query has outputs.  If I'm asking for the manifest, I'm not also
asking for the contents of a given file or patch.  I'd like to move at
least most of the features of annotate into query, and perhaps also some of
the functionality of changes.
-- 
David Roundy
http://www.darcs.net


<Prev in Thread] Current Thread [Next in Thread>