bugGNUstep - Bugs: bug #26280, PrefPane's Info-gnustep.plist file...

 
 

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

bug #26280: PrefPane's Info-gnustep.plist file gets overridden in some cases.

Submitted by:  Jonathan Gillaspie <jonathanosx>
Submitted on:  Tue 21 Apr 2009 09:20:20 PM UTC  
 
Category: MakefilesSeverity: 3 - Normal
Item Group: BugStatus: None
Privacy: PublicAssigned to: Nicola Pero <nico>
Open/Closed: Closed

Sat 10 Oct 2009 03:00:48 PM UTC, comment #4:

Ok ... in trunk I implemented the check and printing a warning. :-)

Thanks

Nicola Pero <nico>
Project MemberIn charge of this item.
Thu 17 Sep 2009 01:51:42 PM UTC, comment #3:

If your expected way to handle it is with a separate file, then that can work. But it still seems a little strange to actually overwrite the file. I would think you would only generate this file when it didn't exist and then just allow developers to modify it from that point on.

Whichever you choose though, a warning or message at compile time would definitely be good. It's particularly confusing that currently only SOMETIMES does the Info-gnustep.plist get overridden. (Namely on the initial build).

Jonathan Gillaspie <jonathanosx>
Project Member
Thu 17 Sep 2009 09:01:54 AM UTC, comment #2:

This seems to be a common problem with gnustep-make, so I need to add code to gnustep-make to detect it and print a friendly explanation of how to fix it.

Thanks

Nicola Pero <nico>
Project MemberIn charge of this item.
Sat 15 Aug 2009 10:21:11 PM UTC, comment #1:

Hi Jonathan

sorry for the late reply.

The problem you're experiencing might be due to a misunderstanding / lack of explanations in the gnustep-make documentation.

I guess I'll quote stuff from gnustep-make --

# If you want to insert your own entries into Info.plist (or
# Info-gnustep.plist) you should create a xxxInfo.plist file (where
# xxx is the bundle name) and gnustep-make will automatically
# read it and merge it into Info-gnustep.plist.

So, you shouldn't create an Info-gnustep.plist file yourself. Create a xxxInfo.plist file instead. gnustep-make will read it, merge it with any additional information it automatically needs to add to create the "official" Info-gnustep.plist, and generate Info-gnustep.plist.

Applications work in the same way; eg, if you check Gorm, you'll see it has a GormInfo.plist with its custom entries; the Info-gnustep.plist is automatically generated by gnustep-make from GormInfo.plist.

Let me know if this is of any help. Sorry again for the very late reply.

Thanks

Nicola Pero <nico>
Project MemberIn charge of this item.
Tue 21 Apr 2009 09:20:20 PM UTC, original submission:

In our project we have a PrefPane bundle, however we have a specific set of information for the Info-gnustep.plist, so we indicate that as a Resource.

Unfortunately the first time we do a make (after a fresh checkout) it appears that make overrides that .plist in the built .prefPane directory with a default file. This seems to ONLY trigger if the make process had to create the .prefPane folder. Ideally it would instead do it ONLY if an Info-gnustep.plist is not there.

Jonathan Gillaspie <jonathanosx>
Project Member

 

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by nico (Posted a comment)
  • -unavailable- added by jonathanosx (Submitted the item)
  •  

    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 2 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat 10 Oct 2009 03:00:48 PM UTCnicoOpen/ClosedOpen=>Closed
    Thu 17 Sep 2009 09:01:54 AM UTCnicoAssigned toNone=>nico

    Back to the top


    Powered by Savane 3.1-cleanup1