-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerrit P. Haase wrote:
> http://anfaenger.de/cygwin/re2c/re2c-0.9.1-1.tar.bz2
BTW: I vote pro this package, I was about to ITP it myself, actually 0=)
- --
L a p o L u c h i n i
l a p o @ l a p o . i t
w w w . l a p o . i t /
http://www.megatokyo.
On Wed, 19 May 2004, Max Bowsher wrote:
> Gerrit P. Haase wrote:
> > Hi Max,
> >
> >> The build does work, but I why modify lnconf.sh ? IMO, the point of
> >
> > It doesn't work for me as it is. I think it should be inlined in the
> > generic-build-script so you may choose to call conf or lnconf
Hi Max schri
> The original intent (AFAICS) was for you to be able to simply use
> the contents of lnconf.sh as ${srcdir}/configure, and then use an
> unmodified g-b-s. Unfortunately, that plan is spoilt, because patch
> doesn't restore the execute mode on new files. You can avoid
> that by callin
Gerrit P. Haase wrote:
> Hi Max,
>
>> The build does work, but I why modify lnconf.sh ? IMO, the point of
>
> It doesn't work for me as it is. I think it should be inlined in the
> generic-build-script so you may choose to call conf or lnconf at any time
> simply by changing the list for the 'all'
Hi Max,
> The build does work, but I why modify lnconf.sh ? IMO, the point of
It doesn't work for me as it is. I think it should be inlined in the
generic-build-script so you may choose to call conf or lnconf at any time
simply by changing the list for the 'all' target.
> having a standard is s
Hello Max,
you wrote:
> The package does build now, but I think it would be best to follow
> Igor's comments about lnconf.sh. The package should not unpack
> files to /usr/src that do not contain the package's name and
> version, to guarantee that they will not conflict with other packages.
Ok, I
Gerrit P. Haase wrote:
> Hello Max,
>
> you wrote:
>> The package does build now, but I think it would be best to follow
>> Igor's comments about lnconf.sh. The package should not unpack
>> files to /usr/src that do not contain the package's name and
>> version, to guarantee that they will not conf
Hello Max,
you wrote:
> The package does build now, but I think it would be best to follow
> Igor's comments about lnconf.sh. The package should not unpack
> files to /usr/src that do not contain the package's name and
> version, to guarantee that they will not conflict with other packages.
Ok, I
