Re: [Cgdb-devel] cgdb for Cygwin available

[Ronald Landheer-C. <bly...@us...>]

As far as the build scripts are concerned: I'm a bit hesitant about adding a
directory to a CVS repository that I'm not in charge of, so I'll leave the
directory-making up to you and put the script where you tell me to :)

As for the changes on the branch: they're done - you can merge them whenever
you want. Note that the only important changes are to the not-generated files
but everything's in the ChangeLogs so merge away :)

As for the different versions of the Autotools: I developed my changes on a 
Gentoo box with a relatively old set of Autotools, and used them on a Cygwin
box with the latest versions - I don't think there will be any problem. Note,
though, that there is a minor issue that the packaging script works around:
the files that shouldn't be installed (the executables) are, by default, 
into the builder's home directory. This is not a good idea, of course, but
is caused by the special handling of those programs in the Makefile.am files
(the noinst_bin_PROGRAMS parts). This wouldn't normally be a problem, but
it is when you use the DESTDIR variable to put the installation elsewhere,
which I do when packaging. IMHO, these lines should simply be removed from 
the Makefile.am files and be replaced by a cleaner way of handling things. 
If you want, I can see what I can do about this (but as for the Cygwin distro
this wasn't necessary, I didn't do anything about it ;)

Should you run into any problems with the patches, please let me know and I'll
try to fix the problem in the branch (or do a merge locally and fix it in the
merged version).

rlc

On Mon, Dec 15, 2003 at 10:42:37AM -0500, Bob Rossi wrote:
> > I've just put cgdb-0.4.0-1 on rlc.unsane.co.uk. You can point to it with 
> > Cygwin's Setup program to install it.
> 
> Thanks for the great work!
> I'm on vacation in Florida, but I'll try installing it when I get back.
> 
> > All necessary changes are in the Cygwin release branch in CVS.
> > One question, though: would you like to have the packaging script in CVS 
> > as well?
> 
> That is a great idea. You could make a new directory for package 
> maintainers. Possibly a directory in there for each distribution. That
> would be up to you, since you probably know how involved it is to make
> a package for a distro. We could store the Cygwin/debian and maybe 
> gentoo ( Mike :) ) packaging scripts.
> 
> Let me know when you are done so I can merge the branch back into the
> main trunk. I do have one concern for when I do the merge. I think it
> might be possible that when I merge the branch and rerun the
> autoconf/automake tools, that we are not guaranteed to know if your
> changes still work properly. (I am using a different version of the 
> auto tools ). What is a good way to make sure that your changes do 
> still work?
> 
> Thanks,
> Bobby



-- 
QOTD:
	"She's about as smart as bait."