[pkg-GNUstep-maintainers] GNUstep fucking

Dan Weber dan@mirrorlynx.com
Sat, 26 Jun 2004 22:58:11 -0400


This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigA0F2D1EE38CBF3E1B9281146
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Gürkan Sengün wrote:
> hi
> 
> 
>>- openapp is a binary that people execute directly, so it must be in
>> /usr/bin/; it is a serious bug if they are not.
> 
> i think we should use "open" from the Backbone project, that is the successor
> of openapp. and put it in /usr/bin
> 
Too many tools are already named open.  If thats the case rename it to 
open.gnustep even.

> evan, i don't mind, either you or me (or together with co-maintainging) we
> use backbone cvs snapshots and generate four packages:
> backbone-open, backbone-terminal, backbone-textedit, backbone-preferences
> if you want we can also call them .app (but not the open tool, what will them be called? (package name)). i would still prefer call it what they are called upstream, i.e terminal. or rather termanal textedid etc... 
> 
> real gnustep people seem to use / as their root and ahve /System, /Volumes ...
> as defined in the standard doc of linuxstep.... 
> 
This is debian, not linuxstep.
> 
>>- architecture-independent files must be in /usr/share; it is a serious
>> bug if they are not.
> 
> splitting and cluttering a gnustep.app/ package across the file system is
> seriously wrong and against gnustep (openstep,nextstep) philosophy and idea.
> there must be a way to follow the specifications and standards for GNUstep.
> users will be fucked when you give them something that is not GNUstep and you
> call it GNUstep. if you really want to distribute the files across the filesystem do so BUT DO NOT CALL THAT GNUSTEP!
>
You are integrating GNUstep into an existing operating system. 
Following Operating System standards is optimal.

> i recommend people source GNUstep.sh in /etc/profiles. if people do this,
> do the gnustep-make wrappers scripts still work? i recall having had problems
> with this. eric/doko can you check this?
> 
Sourcing scripts as described in Steve's first email is against policy.

> some of my gnustep packages have wrapper scripts in /usr/bin or /usr/games
> some do not. the mass bug filing sucked. one mail for one message would have been enough. 
> 
Sorry about the bugs reports that may have been filed against FHS 
compliant packages.  Based on the facts that most incompatible are 
dependant on gnustep-base1 or gnustep-make is how I chose packages to 
bug report upon.
> cheers,
> gürkan sengün
> 

Dan Weber

--------------enigA0F2D1EE38CBF3E1B9281146
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFA3jfGF6i3K/AxoQERAsRgAJ0W38YwkI8CiWxm6Z5ETc1rmicJYgCcDJ0z
CIkf5ejuRSaSKzqHvEqoay8=
=IBfD
-----END PGP SIGNATURE-----

--------------enigA0F2D1EE38CBF3E1B9281146--