Re: [gentoo-dev] Re: Re: Why isn't /root/.bash_profile in the stage tarballs?

2007-09-24 Thread Mike Frysinger
On Saturday 22 September 2007, Andrew Gaffney wrote:
 Steve Long wrote:
  Great. What exactly? How does fulfilling the user requirement with
  vapier's solution mess up catalyst?

 This is the the first time I've heard of a user requesting this change. It
 seems to me that many people prefer to *not* have a .bash{rc,_profile} in
 /root

sure, people with irrational (from the point of Gentoo) fears

actually read the default files and you'll see they're pretty much helpful 
explanatory comments ... except for the logout file where it runs `clear` and 
no one wants *that* for root

 which is the way it's always been.

on Gentoo, yes, it's been this way *so far*, but not for other distros

 Why not just add the ability to  
 copy these files with 'emerge --config' to certain ebuilds, and then add a
 note to the handbook telling users to run the command if they want to?

running commands to get a sane default is not user friendly

 Even better, just tell the users to run 'cp -a /etc/skel/* /root/' if they
 really want the stuff, and not modify any ebuilds at all?

since it wont work at all ... i dont think ive ever seen /etc/skel/ have 
something which didnt start with a .
-mike


signature.asc
Description: This is a digitally signed message part.


[gentoo-dev] Re: Re: Why isn't /root/.bash_profile in the stage tarballs?

2007-09-22 Thread Steve Long
Chris Gianelloni wrote:

 On Sat, 2007-09-22 at 08:01 +0100, Steve Long wrote:
  I've already stated my preference for not doing *anything* outside of
  merging packages in the stages.
 With respect, this is a little confusing. I didn't get past the learning
 curve for catalyst, but it's clearly not the same as simply merging
 packages, or you wouldn't need a special tool.
 
 The tool does things like setting up the chroot.  The code run by
 catalyst to get a stage3 from a stage2, not counting things like chroot
 setup, is emerge -e world just like going from a stage2-stage3 by
 hand.  Anyway, you don't really need to understand it, as I do, and
 vapier does.  If you're really interested, learn a bit about catalyst.
 Uninformed opinions help no one.

So I don't need to understand it do understand the argument, or I do?
Thanks for conceding that it does a little bit more than merging packages,
in any case.
 
 It seemed to me that a clean, *simple* solution which would work for any
 future packages that might also need this functionality was proposed. Why
 not just use it? It's only one command, and the standardisation would
 mean users could rely on the mechanism for system recovery.
 
 Uhh... what does adding emerge --config have to do with catalyst?
 There's nothing stopping vapier/anyone from adding the emerge --config
 steps to the ebuilds.  I simply said that I'm not wanting to add code to
 run those to catalyst for the reasons I have already stated.  In no way
 does that impact the usefulness of the config code for end users.  It
 only affects what goes into the stages.

Well clearly it's affected at least one user (or was it a dev; it doesn't
matter does it really?) who stated it affects others. If vapier's solution
of adding *one* command line to catalyst doesn't fulfil the user
requirement, could you state how?

 Or am I missing some deeper technical implication?
 
 Yup.
 
Great. What exactly? How does fulfilling the user requirement with vapier's
solution mess up catalyst?


-- 
[EMAIL PROTECTED] mailing list



Re: [gentoo-dev] Re: Re: Why isn't /root/.bash_profile in the stage tarballs?

2007-09-22 Thread Andrew Gaffney

Steve Long wrote:

Great. What exactly? How does fulfilling the user requirement with vapier's
solution mess up catalyst?


This is the the first time I've heard of a user requesting this change. It seems 
to me that many people prefer to *not* have a .bash{rc,_profile} in /root, which 
is the way it's always been. Why not just add the ability to copy these files 
with 'emerge --config' to certain ebuilds, and then add a note to the handbook 
telling users to run the command if they want to?


Even better, just tell the users to run 'cp -a /etc/skel/* /root/' if they 
really want the stuff, and not modify any ebuilds at all?


--
Andrew Gaffney http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer Catalyst/Installer + x86 release coordinator
--
[EMAIL PROTECTED] mailing list



Re: [gentoo-dev] Re: Re: Why isn't /root/.bash_profile in the stage tarballs?

2007-09-22 Thread Arfrever Frehtes Taifersar Arahesis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

2007-09-22 21:57:43 Andrew Gaffney napisaƂ(a):
 Even better, just tell the users to run 'cp -a /etc/skel/* /root/'

Rather:
cp -a /etc/skel/{*,.[^.]*,..?*} /root

- -- 
Arfrever Frehtes Taifersar Arahesis
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.7 (GNU/Linux)

iD8DBQFG9Xab/axNJ4Xo/ZERAq4cAKCNrdHT3G3QrRF+LVyAXP3+QhwB4ACfZz8S
0axPBQmlUNdYHfgHD1jp+Ro=
=KW3v
-END PGP SIGNATURE-
-- 
[EMAIL PROTECTED] mailing list