packaging cswcommon

[Dagobert Michelsen]

Hi Carsten,

Am 17.12.2015 um 09:47 schrieb Carsten Grzemba <grzemba at contac-dt.de>:
> I try to puzzle out how to package cswcommon for IPS

I would try to drop CSWcommon in IPS, it serves almost no purpose.
It is essentially directory stubs, pkg-hooks which are not there in IPS,
links from lib/64 to lib/sparcv9 which can be shipped by each package
and thats it.

> in gar.pkg.mk is a line
> 
> $(PROTOTYPE): $(WORKDIR) merge
>     $(_DBG)cswproto $(if $(INCLUDE_COMMONDIRS),,-c $(GARDIR)/etc/commondirs-$(GARCH)) -r $(PKGROOT) $(PKGROOT)=$(if $(ALLOW_RELOCATE),,'/') >$@
> 
> so that cswproto can generate the common dirs.
> But variable INCLUDE_COMMONDIRS is used nowhere and now there is a script build_common.sh in cswcommon recipe so I assume that cswproto do not generate the common dirs and links.
> 
> But I like the idea to have the variable INCLUDE_COMMONDIRS in recipe of cswcommon because that is the only package which should have the common paths.

I would reverse the logic for IPS and include commondirs in each package and not depend
on CSWcommon at all.


Best regards

  — Dago

--
"You don't become great by trying to be great, you become great by wanting to do something,
and then doing it so hard that you become great in the process." - xkcd #896

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.opencsw.org/pipermail/maintainers/attachments/20151217/739d4497/attachment.asc>