bugGNUstep - Bugs: bug #5601, Exported variables ($PATH and...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

bug #5601: Exported variables ($PATH and $GNUSTEP_*)

Submitted by:  Invalid User ID <Invalid User ID>
Submitted on:  Sun 28 Sep 2003 05:45:41 AM UTC  
 
Category: MakefilesSeverity: 1 - Wish
Item Group: Change RequestStatus: None
Privacy: PublicAssigned to: Nicola Pero <nico>
Open/Closed: Closed

Wed 31 Mar 2004 11:40:43 AM UTC, comment #2:

I've removed GNUSTEP_NETWORK_ROOT by default. That should
reduce clutter considerably. Other changes pending or
future changes will reduce the clutter even more.

Thanks

Nicola Pero <nico>
Project MemberIn charge of this item.
Mon 29 Sep 2003 10:35:36 AM UTC, comment #1:

Hello. Thanks for your feedback. :-)

> Directories that don't exist shouldn't be added.


The reason why we add directories that don't exist yet is that if you create the directories and install something
(a program) in them, they are immediately available, without the need for rerunning GNUstep.sh.

For example, $GNUSTEP_LOCAL_ROOT/Tools is added to the PATH
even if empty or non-existing. So if you now download a tool from the net, compile it and install it (the tool will
by default create and install itself in $GNUSTEP_LOCAL_ROOT/Tools), then you can
run the tool immediately - it's automatically in your PATH.

If GNUstep.sh were filtering out empty/non-existing dirs, you'd have to manually rerun GNUstep.sh to be able to run the tool.

Moreover, you can mount/unmount entire GNUstep trees from remote networks (say, you mount GNUSTEP_NETWORK_ROOT from
a central server in your company); the corresponding tools
/applications will appear/disappear transparently as you
mount/umount the tree.

This functionality was felt to be so cool :-) that it's Ok
to have a few links to empty directories.

What GNUstep.sh already does is that, if GNUSTEP_LOCAL_ROOT == GNUSTEP_NETWORK_ROOT, for example, then it doesn't add the directory twice but only once. If you're very worried about having multiple dirs, you could play with the gnustep-make ./configure flags to remove GNUSTEP_NETWORK_ROOT, for example.

The other point - reducing the number of variables exported by GNUstep.sh - is generally a good thing, but it's not easy as most of them are actually used / in use (often by 3rd party software).

The only one which looks pointless and possibly nobody
is using it is GNUSTEP_ROOT. I'll investigate if we can remove that. :-)

Nicola Pero <nico>
Project MemberIn charge of this item.

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

CC list is empty

 

Do you think this task is very important?
If so, you can click here to add your encouragement to it.
This task has 0 encouragements so far.

Only logged-in users can vote.

 

Please enter the title of George Orwell's famous dystopian book (it's a date):

 

 

Follow 4 latest changes.

Date Changed By Updated Field Previous Value => Replaced By
Wed 31 Mar 2004 11:40:43 AM UTCnicoOpen/ClosedAnalyzed=>Closed
Mon 29 Sep 2003 10:35:36 AM UTCnicoSeverity3 - Normal=>(Error - Not Found)
  Assigned toNone=>NA
  Open/ClosedOpen=>(Error - Not Found)

Back to the top


Powered by Savane 3.1-cleanup1