Hi,
On Sun, Mar 24, 2013 at 05:18:46PM +0100, Vincent Lefevre wrote:
> On 2013-03-25 00:56:18 +0900, Osamu Aoki wrote:
> > What environment problem? Let me see:
> >
> > On 2013-03-23 22:04:42 +0100, Sébastien Villemot wrote:
> > > I beg to disagree. It's not up to the package build system to verify
> > > that the PATH contains /bin and /usr/bin, or that no core utility is
> > > overridden by some custom binary in the PATH. Otherwise almost all
> > > packages in the Debian archive are buggy.
> >
> > Yah, if one sets up an insane customization, even debuild will fail.
>
> This is going completely silly. What Sébastien is saying is bullshit.
> My $PATH does contain /bin and /usr/bin, and no core utilities are
> overridden. What made the build fail is just a "." at the *end* of
> $PATH. If Debian's build system is confused by that, it is really
> broken.
>
> [...]
> > Having said it and also having seen some highly skilled DD hitting this
> > insane build environment situation, so what is needed is to add note as
> > follows in nicer text:
FYI: This "some highly skilled DD" is neither ones discussion this bug. But
someone else very respected in project.
> > * No strange customization of the build system.
> > ** PATH
>
> I disagree. A user should be allowed to have his own $PATH (with
> some obvious conditions).
Yah, a user is allowed to have his own everything. More over, csh, zsh,
rc, ... any shell he likes.
> > ** locale
>
> Ditto, the user should be allowed to use any locale provided by
> the system. Developers should be aware of settings like LC_ALL=C
> (or C.UTF-8, because some utilities are broken in non-UTF8
> locales) when needed (ideally the build system shouldn't be
> locale-sensitive).
But *PACKAGE BUILD ENVIRONMENT* is not the same thing as the user's
normal shell working environment. We must use sanitized build
environment.
I think this is what you are missing. Now i have better idea what kind
of precaution words to use.
Osamu
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
