[Gtkradiant] Permission errors (2)

Timothee Besset ttimo at ttimo.net
Mon Sep 2 09:39:38 EDT 2013


Hey Bebo,

GtkRadiant should have write permissions to the directory it is installed
in. This is really the easiest way you are going to package GtkRadiant for
a particular distribution.

I believe that packaging systems should provide the operating environment
that a piece of software requires, and not the other way around. I'm not
sure these lines of code you are pointing to are actually a problem for
what you are trying to do, that looks like BSP code to me. But I'm sure
there are plenty of other places that would need to be changed if we were
going to try and make radiant run from a readonly directory.

The thing is, none of the developers seem very interested in helping with
that effort. It would likely destabilize the codebase, introduce new bugs
for no obvious advantage. We've already put significant effort in being
able to provide a set of binaries that run on a variety of Linux systems,
and can be distributed in a zip, without having to deal with distribution
specific package requirements.

I believe this strategy is a much better approach for GtkRadiant, and while
I wouldn't actively prevent someone from doing distribution-specific
packaging if they want to spend their energy doing so, it seems like the
other developers active on the project generally agree with me.

Cheers,
TTimo



On Mon, Sep 2, 2013 at 5:11 AM, bebo_sudo <bebo.sudo at gmail.com> wrote:

> Hi all folks,
> I still am going to write about packaging gtkradiant for fedora.
>
> Referring to the last mail I sent at the ML about the permission errors
> [1], I searched in github the relative code [2] and I think the "bug" is
> around the 71th line of this [3] or this [4] file (which are equal?):
> ...
>
>         /* write it */
>         Sys_Printf( "Writing %s\n", filename );
>         Sys_FPrintf( SYS_VRB, "(%d bytes)\n", bspEntDataSize );
>         file = fopen( filename, "w" );
>
>         if ( file == NULL ) {
>                 Error( "Unable to open %s for writing", filename );
>         }
>
>
> I'm not a C programmer and do not know how difficult it would be to create
> a shortcut (a symlink, or something else) to the user home instead of
> writing in the containing folder, but if there's someone who's able to
> solve this issue I would appreciate it very much.
>
> Thanks anyway,
> bebo
>
>
> [1]: http://icculus.org/pipermail/**gtkradiant/2013-February/**011841.html<http://icculus.org/pipermail/gtkradiant/2013-February/011841.html>
> [2]: https://github.com/TTimo/**GtkRadiant/search?q=+unable+**
> open+writing&type=Code<https://github.com/TTimo/GtkRadiant/search?q=+unable+open+writing&type=Code>
> [3]: tools/quake3/q3map2/**exportents.c
> [4]: tools/urt/tools/quake3/q3map2/**exportents.c
> ______________________________**_________________
> Gtkradiant mailing list
> Gtkradiant at icculus.org
> http://icculus.org/mailman/**listinfo/gtkradiant<http://icculus.org/mailman/listinfo/gtkradiant>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://icculus.org/pipermail/gtkradiant/attachments/20130902/b57de109/attachment.html>


More information about the Gtkradiant mailing list