installpkg messing up perms
in [Slackware]
|
From: Sylvain Robitaille on 13 Jul 2010 11:01 Grant wrote: > ... A SlackBuild script allows you to make a package, ... as root. > > On a root account, no su madness, a proper root login. This all suggests, however, that perhaps the scripts at Slackbuilds.org don't explicitly set a umask, and I would argue that this is an oversight that should be corrected. There's no reason anyone should have to *login* as root, rather than simply use su or sudo, to get the expected result. More importantly, there's no reason that a root environment should be predictable. The scripts should explicitly set whatever environment they expect to have. -- ---------------------------------------------------------------------- Sylvain Robitaille syl(a)encs.concordia.ca Systems analyst / AITS Concordia University Faculty of Engineering and Computer Science Montreal, Quebec, Canada ----------------------------------------------------------------------
From: Sylvain Robitaille on 13 Jul 2010 11:04 Dario Niedermann wrote: > ... I didn't think/know at the time that the issue was related to > installpkg. It isn't. It's related to the packages you built and have installed. -- ---------------------------------------------------------------------- Sylvain Robitaille syl(a)encs.concordia.ca Systems analyst / AITS Concordia University Faculty of Engineering and Computer Science Montreal, Quebec, Canada ----------------------------------------------------------------------
From: Franz Sauerzopf on 13 Jul 2010 12:08 Am Tue, 13 Jul 2010 16:33:00 +0200 schrieb Helmut Hullen: > > If I would run > cd / > installpkg /path/to/cmus-v2.2.0*.txz > > nothing bad would happen. > As far as I read this conversation, the OP is building the SlackBuilds via sudo, in contrast to calling them as root, as intended. He would like to make this also possible. A reasonable response given by Sylvain a few messages above this one, was not further considered in this thread. I cannot be helpful there, but I just wanted to point out the misunderstanding. Have fun Franz
From: Dario Niedermann on 13 Jul 2010 12:12 Sylvain Robitaille <syl(a)alcor.concordia.ca> wrote: > Dario Niedermann wrote: > >> ... I didn't think/know at the time that the issue was related to >> installpkg. > > It isn't. It's related to the packages you built and have installed. If the packages are "broken" (i.e. for whatever reason they contain system directories with non-sane permissions) installpkg should IN MY OPINION handle the case gracefully, rather than blindly screw things up. In general, regardless what a package might say, I really don't see why a package installer should touch permissions on directories like '/', '/usr', '/etc'. Installpkg is the only package installer I've seen in my life that will do this. -- > head -n1 /etc/*-{version,release} && uname -moprs Slackware 12.2.0 Linux 2.6.27.7-crrm i686 AMD Turion(tm) 64 Mobile Technology MK-36 GNU/Linux
From: Joost Kremers on 13 Jul 2010 12:32
Dario Niedermann wrote: > I'm not installing self-made packages: the problems I described came > from packages made by Slackbuilds downloaded from slackbuilds.org. in that case, you *are* sort-of installing self-made packages, because the Slackbuild scripts you downloaded are run and create packages on your machine. you may not have written the build script yourself, but in essence you *are* the one creating the package. -- Joost Kremers joostkremers(a)yahoo.com Selbst in die Unterwelt dringt durch Spalten Licht EN:SiS(9) |