From: Bruno C. <Bru...@hp...> - 2007-10-26 13:37:19
|
Hello Bryan and others, Bryan Gartner said on Fri, Oct 26, 2007 at 06:25:02AM -0600: > On Thu, Oct 25, 2007 at 10:34:06PM +0000, Cornec, Bruno (Linux Consultant) wrote: > > The problem is that this should be rather done a run time than at build > > time, because the machine on which you're building the tool may be > > different from the machine you want to install it on. > > And if you are installing from CVS/tar, this is a "runtime" check, which > I'd prefer not to lose the ability to do. So, I vote to retain the > checks there. OK, so I'd like to propose an alternative that may help both of us: Could we do the check after the make integrate phase (e.g. a make check new order) that would have to be called in the context of tar.gz install (by Creating a cheked dummy file in the tree, that could be verified before running anything). If there go on, if not, emit a warning rather than running with CGI-Carp or something like that. Of course that file could be touched by the spec/rules files to avoid problems. WDYT ? > > FYI, I have generated a lot of RPMS today, available at > > ftp://ftp.project-builder.org , except that the main one, > > linuxcoe-sd-base is missing :-( > > Nice job! Nearly ;-) And I still have problems for the .deb, partly because of the lack of changelog files. Bruno. -- Linux Profession Lead EMEA / Open Source Evangelist \ HP C&I EMEA IET http://www.mondorescue.org / HP/Intel Solution Center \ http://hpintelco.net Des infos sur Linux? http://www.HyPer-Linux.org http://www.hp.com/linux La musique ancienne? http://www.musique-ancienne.org http://www.medieval.org |