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

[Sylvain Beucler-4]

URL:
  <http://savannah.gnu.org/bugs/?26280>

                 Summary: PrefPane's Info-gnustep.plist file gets overridden
in some cases.
                 Project: GNUstep
            Submitted by: jonathanosx
            Submitted on: Tue 21 Apr 2009 09:20:20 PM GMT
                Category: Makefiles
                Severity: 3 - Normal
              Item Group: Bug
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

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.






    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?26280>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/



_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@...
http://lists.gnu.org/mailman/listinfo/bug-gnustep

[Sylvain Beucler-4]

Follow-up Comment #1, bug #26280 (project gnustep):

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

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?26280>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/



_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@...
http://lists.gnu.org/mailman/listinfo/bug-gnustep

[Sylvain Beucler-4]

Update of bug #26280 (project gnustep):

             Assigned to:                    None => nico                  

    _______________________________________________________

Follow-up 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

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?26280>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/



_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@...
http://lists.gnu.org/mailman/listinfo/bug-gnustep

[Sylvain Beucler-4]

Follow-up Comment #3, bug #26280 (project gnustep):

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).


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?26280>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/



_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@...
http://lists.gnu.org/mailman/listinfo/bug-gnustep

[Sylvain Beucler-4]

Update of bug #26280 (project gnustep):

             Open/Closed:                    Open => Closed                

    _______________________________________________________

Follow-up Comment #4:

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

Thanks

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?26280>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/



_______________________________________________
Bug-gnustep mailing list
Bug-gnustep@...
http://lists.gnu.org/mailman/listinfo/bug-gnustep