Ben Finney writes:
> I believe the documentation directory is the right place to add
> package-specific information. I retract my earlier suggestion of a
> static manifest file; that information is best generated directly from
> the package database.
Yes. If something is particularly contrary to
Herbert Xu writes:
> > dash$ FOO=$(false) && echo worked
> > worked
>
> This is definitely a (recent) bug in dash.
Thanks. Could you point me to where the correct behavior is specified?
--
things change.
[EMAIL PROTECTED]
(I'm not sure where to send this, but it's of interest for making
packages containing shell scripts policy-compliant, which I'm currently
trying to do, so...)
bash and dash differ in their handling of variable assignments. To wit:
bash$ FOO=$(false) || echo failed
failed
dash$ FOO=$(false)
Manoj Srivastava writes:
> dpkg may well have problems with the symlink, so any packages still
> installing in /usr/doc/ could cause problems with dpkg.
> Since the move is likely to take a long time, this grand
> move-in-one-fell-swoop is likely to be fraught with problems.
This is a weak argume
4 matches
Mail list logo