[issue1337] HEAD can't build 2.2-RELEASE

["Stathis Kamperis \(via DragonFly issue tracker\)" <sinknull@xxxxxxxxxxxxxxxxxxxxxxx>]

Stathis Kamperis <ekamperi@gmail.com> added the comment:

Salute.

Let me summarize where we stand. Back porting the env(1) changes to the 2_2 branch:

1) unbreaks the build *solely* of 2.2 under -current.
2) it doesn't affect (i.e., break) the build of 2.2 under a 2.2 host system
3) it doesn't affect (i.e., break) the build of 2.2 under a 2.0 host system

(Mind that I didn't back port the patch to 2_0, so I can't comment on it)

: I'm not sure which guarantees we have on building old DragonFly releases
: on newer system, but it sure is a nice feature. Is it documented some place?

I don't know either, but I'm really new here. Anyone ?

I would expect to be able to build the exact previous release from where I am,
e.g. if the host is 2.2 be able to build 2.0. Not sure if it's desired to go
further in the past and build -say- 2.0 under -current.

: Re. multiple '=' in env(1) assignment: SUSv3 setenv(3) says that variable name
: isn't allowed to contain '='. So your test below mixing new env(3) with old
: setenv(3) shows that correct assignment is made (to foo).

Yes you are right. I got ashtray by printenv(1).

Regarding the possibility to ap/prepend '=' to name/value when calling
setenv(3), this stays unaffected given that patch in discussion touches only env(1).

: I do feel it a little backwards to change old source to get it build on HEAD;
: it will also only solve problem in revisions where change is made,

I'm not excited either, but given the circumstances, this was the best I could
come up with.

Cheers,
Stathis

_____________________________________________________
DragonFly issue tracker <bugs@lists.dragonflybsd.org>
<http://bugs.dragonflybsd.org/issue1337>
_____________________________________________________