#388 closed task (fixed)
make it easier to sync files from yat
Reported by: | Peter Johansson | Owned by: | Peter Johansson |
---|---|---|---|
Priority: | major | Milestone: | svndigest 0.7 |
Component: | build | Version: | trunk |
Keywords: | Cc: |
Description
We have a bunch of files that come from yat, for example, the Option files. I noticed that some of these files have been updated in yat (bug fixes) and these fixes have not propagated to svndigest.
I suggest that we create a fetch
target that will donwload the files using for example wget. This implies that we should keep the files as is, which explicitly means they should stay in their namespace, theplu::yat::utility
, and I also think we should let the svn:keyword reflect properties in yat repository.
With a modern svn server, I think it would be possible to do these connection, but unfortunately I suspect our server is too old. For old servers it is only possible to do these synchronization per directories.
Perhaps, we should keep these files in a separate directory, e.g. lib/yat
but I have no preference on that.
Minor detail is that I think we should set svndigest:ignore on these files which also implies that svndigest will not try updating copyright status. In other words the files belong to the yat project.
Change History (4)
comment:1 Changed 14 years ago by
Status: | new → assigned |
---|
comment:2 Changed 14 years ago by
comment:3 Changed 14 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
(In [795]) refs #388
Create a sub-directory 'lib/yat' in which files from yat are placed. The files may be updated via 'make fetch', see file README for more details on how to change which files are updated/copied through this mechanism.
The reason we do not use subversion's external mechanism is that we don't want the files to be synchronised with yat automatically. We want the update to be moderated by some developer.
I chose to fetch files using the svn client rather than wget because the svn allows us to get an Id string with information from the yat repository. 'wget' would just download the file as it appears on the server that is the string is not expanded.
The file 'config_public.h' is created by configure just as in yat. This implies that automake adds $(top_builddir)/lib/yat to the include path so unless in a VPATH build $(top_srcdir)/lib/yat is in the include path. As we have already added $(top_srcdir)/lib to the include path, and there are both a lib/utility.h and a lib/yat/utility.h it is not obvious which file is included when having 'include "utility.h"'. For this reason, when being in bin/ and test/ it is needed to include "../lib/utility.h" rather than "utility.h" when we want to include 'lib/utility.h'.