-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9/11/10 5:57 PM, Sjors Gielen wrote:
> 
> Op 11 sep 2010, om 23:20 heeft David Lowe het volgende geschreven:
> 
>> "#   chgrp "" "$(DESTDIR)$(bindir)/angband"
>> #    chmod g+s "$(DESTDIR)$(bindir)/angband"
> 
> By the way,
> 
> Now that Fink builds as nobody by default (or was this just proposed?)

proposed only, for now.

 - what's the policy on packages requiring build-as-root purely because
of a chgrp / chmod?

I think this is also the sole reason why dpkg and/or apt require build
as root.
> 
> If there's no policy on this, I would like to propose: Put any chgrp and 
> chmod and similar operations requiring root access in the PostInst script. It 
> makes sure the files are installed with the right permissions, while allowing 
> build as any user. I don't see any better way to do it, except requiring root 
> access for some steps.
> 
> Sjors
> 
> 

Seems reasonable.

There's a patch by Daniel Johnson which makes --build-as-nobody the
default option and also implements a BuildAsNobody: field for .info
files.  If you set BuildAsNobody: false, then that flags the package
appropriately.

https://sourceforge.net/tracker/?func=detail&aid=3044604&group_id=17203&atid=317203
- -- 
Alexander Hansen
Fink User Liaison
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkyMAY0ACgkQB8UpO3rKjQ/2+QCghUeXT0k88lMXbl0lYnHmfBc0
vV4AoICcCT0urHEFoHwdKAqE+iCLa/eO
=/kIa
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to