[gobolinux-devel] Scripts and Compile pre-releases

[Jonas Karlsson]

On 17/04/2008, Carlo Calica <carlo at calica.com> wrote:
> On Tue, Apr 15, 2008 at 10:55 PM, Jonas Karlsson
>
> <jonka750 at student.liu.se> wrote:
>
> > Hello,
>  >
>  >  as Michael announced yesterday here comes the release. Or at least the
>  >  pre-release. This is what will be the release in a couple of days,
>  >  unless something unforseen happens, so please test it in every
>  >  possible way.
>  >  This also means that only fixes _and only fixes_ is commited to
>  >  these two tools in svn.
>  >
>  >  New major features
>  >  Scripts:
>  >  * Use flags
>  >  * "unsudoing"
>  >  * CommandNotFound
>  >
>  >  Compile:
>  >  * Run_Hooks
>  >  * ContributeRecipe
>  >  * Support for Mercurial and Bazaar repositories
>  >  * Support for Cabal packages
>  >
>  >  http://karlsson.sytes.net/gobo/packages/Scripts--2.9.0--i686.tar.bz2
>  >  http://karlsson.sytes.net/gobo/packages/Compile--1.11.0--i686.tar.bz2
>  >
>
>
> There are a number of sudo changes in this release.  To use these
>  properly /Files/Compile should be group sys and permission g+ws.  This
>  is done on 014.01 but it would be nice for these changes to happen on
>  old installs as well.  Unfortunately, Post_Install can't operate
>  outside of $target/$target_settings.  Should there be a check in
>  bin/Compile?  What's the best way?
>
This is an issue I've thought much about, but haven't found a clean solution.
If someone can come up with a clean solution, please post it. We need it. If
no clean solution is found, should we accept a workaround?

To recap the problem:
Most users have used sudo or root to run Compile. This is discuoraged, but
there was no clean way to build some recipes without it before this release
of Compile. Because Compile was run with superuser privileges a lot of
entried in /Files/Compile will be owned by that user and various actions
executed by normal user (which is the recommended way to run Compile)
will fail. We need to prevent that.

-- 
/Jonas