Am Dienstag, den 13.03.2007, 10:21 +0100 schrieb Loïc Minier: > On Tue, Mar 13, 2007, Daniel Leidert wrote: > > Personally I see this as feature. So I can test, without the necessity > > to move files untested under version control. So I would like to > > request, to allow both behaviours. > > I do the same usage as you do. There are three types of files: > - files under version control and unchanged in the WC; these do not > appear in svn status -- these are committed > - files under version control but changed in the WC (added files, > modified files, removed files...); these appear in svn status as "A" > "M" or "D" etc. -- these are not committed > - files not under version control, such as new files which were not svn > added; these appear as "?" in svn status -- these wont be committed > > I know of two types of usage of svn-buildpackage: > - Joss in the GNOME team commits files, and then tests the build; > this often results in more commits, especially with commits fixing > the previous commits > - I personally change files, svn add or svn rm them, do a test build, > and then do the commit; I set svn-ignore-new in > .svn-buildpackage.conf for this to be allowed
I see ... > What I don't like it the handling of the third type of files; these > files should not ever be considered by svn-buildpackages since these > are not in SVN. If you don't plan to add these to the SVN, why would > you build with these files? > > Are you advocating for an option to still be able to build with these > files, the '?' files? Well, I sometimes used to do that. But you are right. You can put files under version control without committing them and you can still test them. This is enough I need. So if it's more intentional to not consider unversioned files for a build, I support your request. So I can finally put my personal TODO files in the SVN directories too :) Regards, Daniel
