Re: bashims in debian/rules
On Fri, Nov 07, 1997 at 02:59:28PM +0100, Santiago Vila Doncel wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
>
> On Fri, 7 Nov 1997, Ian Jackson wrote:
>
> > Roman Hodek:
> > > I think you misunderstood "cross compilation" in the original mail. It
> > > meant compiling Debian packages on a non-Debian system, where sh isn't
> > > bash.
> >
> > I don't think we should attempt to support `cross compilation' in this
> > sense.
>
> I think we should try it *because it is not so difficult*.
I fully agree.
> GNU packages may be built in *any* Unix system, and this is a good thing.
> Use of #!/bin/sh in shell scripts is one of the GNU coding standards.
>
> In this case, I fail to see how much more difficult is:
>
> 1) cp debian/{postinst,prerm} debian/tmp/DEBIAN
>
> than
>
> 2) cd debian && cp postinst prerm tmp/DEBIAN
>
> The work involved to change 1) into 2) is *very* small. The benefits of
> the added portability is greater than this small work.
>
> Of course, if we teach our new developers to write debian/rules files in a
> POSIX way for newly created packages, the cost is zero.
>
> Note that 2) is even shorter than 1)
This is sure a point for you, but the only most important change to the
rules files is #!/bin/bash: if someone want use the curly braces, he can use
they, but he must specify #!/bin/bash and not #!/bin/sh. This is the only
problem, I think, with the ports to Solaris.
[snipped]
Francesco
f.tapparo@vi.nettuno.it
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: