installpkg messing up perms
in [Slackware]
|
From: Dario Niedermann on 13 Jul 2010 15:50 Sylvain Robitaille <syl(a)alcor.concordia.ca> wrote: > Dario Niedermann wrote: > >> "Override" ? > > Re-read what you wrote and tell us again that you weren't suggesting > that. I don't need to re-read anything, it's you who needs to re-read tar's man page. Tar does not force you to extract the whole contents of an archive. I'll repeat the question: is it difficult to pass tar a sanitized list of stuff to extract? > I wasn't blaming tar YOU WROTE: | That would need to be a modification of how tar works, then. BULLSHIT. Tar does NOT enforce full extraction of an archive contents. It's installpkg that uses Tar that way. -- > 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: Dario Niedermann on 13 Jul 2010 15:57 Sylvain Robitaille <syl(a)alcor.concordia.ca> wrote: > You're the one claiming installpkg is broken. If indeed it is, and > you have a fix, let's see it. No way. Since this community is in love with installpkg's current behaviour, this community shall receive no unwanted fix. I'm going to keep any improvement to installpkg strictly private. -- > 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: Sylvain Robitaille on 13 Jul 2010 16:18 Dario Niedermann wrote: > BULLSHIT. Tar does NOT enforce full extraction of an archive contents. > It's installpkg that uses Tar that way. So let's see your patch for installpkg, then. -- ---------------------------------------------------------------------- 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 16:23 Dario Niedermann wrote: > I'm going to keep any improvement to installpkg strictly private. Oh good. The rest of us will carry on blissfully believing that installpkg is working just as it was intended to, then. -- ---------------------------------------------------------------------- Sylvain Robitaille syl(a)encs.concordia.ca Systems analyst / AITS Concordia University Faculty of Engineering and Computer Science Montreal, Quebec, Canada ----------------------------------------------------------------------
From: Robby Workman on 13 Jul 2010 16:43
On 2010-07-13, Dario Niedermann <M8R-cthw2f(a)spamherelots.com> wrote: > William Hunt <wjh(a)prv8.net> wrote: > >> I'd also suggest the OP use tar, with the '-tv' switches, >> to look at the index of a standard Slackware package (or two) >> and compare it against the index of his home-built package. >> Look for differences between the two in the way permissions >> are set within each package (tar file). > > I'm not installing self-made packages: the problems I described came > from packages made by Slackbuilds downloaded from slackbuilds.org. > Leave root's umask at 0022, and/or switch to root properly from your user account, and/or manually set umask to 0022 before using one of the build scripts. This is NOT a problem with the scripts, or is it a problem with pkgtools. -RW |