Declarations such as:
pkgver=2.11# foo
will work, but trimming off the comment (without trimming the trailing
whitespace) will result in an incorrect validation error. Bash automatically
trims this trailing whitespace and does the right thing under the covers,
so we should honor this as well.
This applies to pkgver, pkgrel, and epoch and ensures that any trailing
whitespace outside of the context of the variable declaration itself is
properly trimmed. The Bash parser will ignore this, and so should we.
We don't need to worry about leading space because it would force a
syntax error, or
On Thu, Nov 17, 2011 at 1:09 PM, Dave Reisner wrote:
> Declarations such as:
>
> pkgver=2.11 # foo
>
> will work, but trimming off the comment (without trimming the trailing
> whitespace) will result in an incorrect validation error. Bash automatically
> trims this trailing whitespace and does
On Thu, Nov 17, 2011 at 08:28:27PM -0600, Dan McGee wrote:
> On Thu, Nov 17, 2011 at 1:09 PM, Dave Reisner wrote:
> > Declarations such as:
> >
> > pkgver=2.11 # foo
> >
> > will work, but trimming off the comment (without trimming the trailing
> > whitespace) will result in an incorrect valida
On 18/11/11 12:28, Dan McGee wrote:
On Thu, Nov 17, 2011 at 1:09 PM, Dave Reisner wrote:
Declarations such as:
pkgver=2.11# foo
will work, but trimming off the comment (without trimming the trailing
whitespace) will result in an incorrect validation error. Bash automatically
trims this tr
On 18/11/11 23:35, Dave Reisner wrote:
This applies to pkgver, pkgrel, and epoch and ensures that any trailing
whitespace outside of the context of the variable declaration itself is
properly trimmed. The Bash parser will ignore this, and so should we.
We don't need to worry about leading space
