[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-devel
Subject: Re: [Fwd: [Bug 53345] .bash_profile script is not sourced]
From: Simon Perreault <nomis80 () nomis80 ! org>
Date: 2004-02-26 15:32:11
Message-ID: 200402261032.11483.nomis80 () nomis80 ! org
[Download RAW message or body]
To others who think this thread is not useful: we're discussing whether
Xsession should source .bash_profile. It is KDE development stuff. It might
not be interesting to you, you might think you know the evident truth, but
this still belongs to kde-devel@kde.org.
On February 26, 2004 3:06, James Richard Tyrer wrote:
> But would it be GNU/Linux?
Sure, and even if it was not, it would still be a Unix clone, which is a
supported KDE platform.
> What the current setup does is force Linux users to have
> Bourne-compatible shell scripts for their shell startup. This is not a
> reasonable solution.
Ah, I see what you mean. What's your fix?
> You have the subset and superset reversed. The problem occurs if a Bourne
> Shell tries to run a Bash specific script. Bourne is a subset of Bash.
> Bash is a superset of Bourne. ARGH!
I totally agree with that.
> Talking about standing an argument on its head! What we are forcing on
> GNU/Linux users is that they have to use a "bourne-compatible" script name.
> What I am talking about is to support Bash if that is what the user has
> installed. Don't we do that with other optional packages? The configure
> script should check for that.
Ah, I see what you mean. I think you're right.
> > On my Fedora system, Xsession depends on bash and includes some very
> > bash-specific constructs.
>
> I don't understand, if Bash is the shell you are using, then Bash is the
> shell that your are using. And are you referring to the distro's Xsession
> script or the one that you wrote?
No, I mean that Fedora's Xsession starts with #!/bin/bash and has bash syntax.
---------- END OF DISCUSSION OF .BASH_PROFILE ------------------
----------- INTER-PERSONAL RELATIONSHIPS DISCUSSION FOLLOWS ----
------- STOP READING HERE IF NOT INTERESTED --------------------
> > You *have* to argue with him until both of you agree.
>
> Right. If you check the above, I was engaging in a reasoned argument. My
> next step was to submit a demonstration patch. He flamed me. You should
> be explaining this to him.
Stop whining. Attach the patch to the bug. Continue adding comments to the
bug. Try to reason him. It may fail. You have no other recourse.
> > If you don't agree, then the component maintainer's opinion is trusted.
>
> Ah yes, the seniority system. Whatever happened to the mythical
> meritocracy?
Who else should we trust in that case?
> And in this case when he only choses to be arrogant and insulting? Very
> unprofessional of him don't you think?
Then in that case you're free to fork.
> > So if you can't convince Oswald,
>
> So, it is about politics rather than the merit of the solution.
The merit of the solution is not evident. The merit of Oswald is evident: he's
been an excellent maintainer for a long time. The merit of the solution can
be demonstrated by forking and gaining a large userbase.
> IT WOULDN'T BE KDM-JRT, IT WOULD BE JRT'S: "Xsession" SCRIPT FOR
> GNU/Bash/KDE/Linux.
Yeah, I know, I consider Xsession as being a part of kdm.
> I have already given it to a few people. But, that
> was when KDM install used to really screw up badly. I have my own script
> because I didn't get one when I first installed from source. The make
> install thought that I had a Debian system.
Cool.
--
Simon Perreault <nomis80@nomis80.org> -- http://nomis80.org
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic