The "infrastructure" fragments deal with special types of "wrappers"
called components (WO/GSWCompoents) which need to be
installed/uninstalled in the correct places.
As far as I know, -make currently does not support "Auxiliary"
"infrastructure" make file fragments. I'm not sure if it should
since I
believe you need to know a lot about -make's internals to maintain
them.
On the other hand I understand that it's a burden for Nicola since he
needs to be aware of what these special wrappers are and how they
should
be handled.
But in the end, I believe that the "infrastructure" might be tied much
closer to the overall -make (i.e. FHS) logic, that I simply isn't
feasible to export that logic to external packages...
Nicola, what do you think?
It's possible, and it would be nice, to separate out the "new project
types"
that are added by some software. For example, gswapps and gswbundles
as added by gsweb, woapps as added by SOPE, palettes as added by
Gorm, etc.
All of these are actually based around the basic types (applications/
bundles/frameworks/libraries/tools)
but add some tweaks or twists of their own.
Unfortunately, defining/standardizing how you can extend the basic
project types etc
is quite a lot of work and in practical terms it would mostly be done
to move gswapp.make
and gswbundle.make out of gnustep-make and into gsweb. It seems to
much work for
almost no gain - so I think I'll spend my time on something more
useful ;-)
But, yes, longer term when we have exhausted every other possible task
(lol) it would be cool
to do this :-)
Thanks
_______________________________________________
Gnustep-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnustep-dev
