Index: [thread] [date] [subject] [author]
  From: Marcus Sundberg <mackan@stacken.kth.se>
  To  : ggi-develop@eskimo.com
  Date: Sat, 29 Aug 1998 14:53:58 +0000

Re: questions about kgicon and libggi

Neal Tucker wrote:
> 
> Marcus Sundberg says:
> > Neal Tucker wrote:
> > >
> > > Andrew Apted says:
> > > > That's a problem with the anonymous CVS repository.  AFAIK, the tarballs
> > > > on the FTP site _do_ have the correct permissions.
> > >
> > > No, this is not the case (I am looking at devel from 0828).
> > > The exec bits are still not set.
> >
> > Then your tar is broken. exec bits _are_ set in the FTP archives.
> > (specificly the 0828 snapshot which I just DLed)
> 
> No, they're not.
> 
> [root@butcher]# tar tzvf ggi-devel-980828.tar.gz degas/kgicon/kgi/configure
> -rw-rw-rw- ggi/ggi        5693 Aug 22 00:34 1998 degas/kgicon/kgi/configure
> [root@butcher]#
> 
> I checked this with:
> GNU tar 1.11.8
> GNU tar 1.12
> the tar from SunOS 5.5.1, which won't tell me its version
> 
> I think my tar is not broken.
> 
> Out of the 45 files called "configure" or ".configure", there are
> 10 that do not have the execute permissions set:
> 
> degas/kgicon/kgi/configure
> degas/kgicon/kgi/accel/Cyrix/.configure
> degas/kgicon/kgi/accel/Matrox/.configure
> degas/kgicon/kgi/accel/WD/.configure
> degas/kgicon/kgi/chipset/ATI/.configure
> degas/kgicon/kgi/chipset/.configure
> degas/kgicon/kgi/clock/prog/.configure
> degas/kgicon/kgi/ramdac/ATI/.configure
> degas/kgicon/kgi/ramdac/.configure
> degas/lib/libggi3d/configure

Ouch!
Sorry, I didn't check all files.
Chris, could you please fix this.

And Todd T. Fries, where are you????? The CVS mirror needs to
be fixed, _NOW_!!!

> > > Also, something I've been meaning to mention for a while but keep
> > > forgetting is that many many files are mode 666, 664, 777, etc.
> > > This is a major pain because I let other people log into my machine,
> > > so I have to fix this every time.  This is especially bad for source
> > > that I routinely compile and execute as root.
> >
> > Hmm, you're right about that, but that's easily fixed by setting
> > up a proper umask, which you should do anyway.
> 
> Incorrect.  I have a proper umask (077), but when I untar software
> packages, I use the 'p' option because the software package is
> *supposed* to know best what its own file permissions should be,
> and should not rely on my umask.

Libggi works fine even if the w bits are all set...
But you're right, and I agree with you that this should be
fixed if possible, however this needs physical/telnet access
to the CVS repository.

TO DEVELOPERS:
When you commit something - make sure that the permissions
are correct! All files should have 0644 permissions, and
for directories and scripts, or that with 0111.

//Marcus
-- 
-------------------------------+------------------------------------
        Marcus Sundberg        | http://www.stacken.kth.se/~mackan/
 Royal Institute of Technology |       Phone: +46 707 295404
       Stockholm, Sweden       |   E-Mail: mackan@stacken.kth.se

Index: [thread] [date] [subject] [author]