bzr export should have a parameter --include-unversioned to include unversioned files

[Andreas Sommer]

Currently the export command only archives versioned files. There should be an option to include unversioned and ignore files (maybe two distinct parameters?).

[John A Meinel (jameinel)]

I'm going to mark this as a dup of bug #173274 because it seems to be related functionality.

[Jelmer Vernooij (jelmer)]

Can I ask what the use case for this is though? It seems like this would basically make bzr export's behaviour the same as "cp -a".

[Andreas Sommer (andidog)]

Basically you're right, it's "cp -a" but additionally deletes the .bzr folder. The use case for me is a project that can be packaged "as is", but some dependencies are too large for version control. The export --include-ignored would then copy these files, too.

[Parth Malwankar (parthm)]

In the context of the discussion on this patch:
https://code.edge.launchpad.net/~parthm/bzr/173274-export-hooks/+merge/35919

I am going to un-duplicate this bug so that we can create a patch for a 'bzr export --all' or 'bzr export --uncommitted' against this and have further discussion here if needed.
Johns point about --uncommitted having a different meaning from the 'merge --uncommitted' usage seems valid to me, so perhaps we can use --all as the option here? I will start on a patch with --all, we can review the option name either here or when the patch is up for review.

[Parth Malwankar (parthm)]

Taking bug #555613 (which asks for --uncommitted to export uncommitted changes) changes into account. Maybe an option like --files=KIND would be more suitable. The possible values for KIND could be "all" and "uncommitted".

"all" can be much like cp but without ".bzr*" and ignored files.
"uncommitted" can ignore the versioned files from working tree (with uncommitted changes).

[John A Meinel (jameinel)]

There is no associated code with this change, so I'm marking it as no longer In Progress after 1+ years.