ignore local changes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Wishlist
|
Unassigned | ||
Breezy |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
We host a web forum with bzr on launchpad which works quiet nicely. The most annoying issue with bzr is that there is no option to ignore changes on a local file. Let me explain:
* The forum must be installable after checking it out
* The forum software makes some changes to a settings file afterwards
* The forum software requires you to remove the install file
So after installing bzr reports these "uncommited" changes which are not wanted ever to be committed! If we'd commit these the next person could no longer install the forum. It becomes a PITA since you always need to specify which files you want to commit...
What I want is this:
bzr ignore --changes file
So the file stays in bzr for future checkouts but `bzr status`, `bzr diff` etc. wont report the file as changed. This should also support deleted files.
Would be great to see this feature!
Changed in bzr: | |
status: | Triaged → Confirmed |
Changed in brz: | |
status: | New → Triaged |
importance: | Undecided → Wishlist |
Interesting idea. I don't know of this feature in other systems, but perhaps it is useful enough to include.
I will say that *most* people work around it by having a "template" file, which people then copy into the final value. Something like:
project. settings. template <= this file is versioned
project.settings <= this file is ignored (bzr ignore project.settings)
And you are expected to: settings. template project.settings
cp project.
as part of the setup process. If you already have a build step, you could hook in a: settings. template project.settings; fi
if [ ! -e project.settings ]; then cp project.
Or at least something like that.