mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] dependencies with collections
Date: Tue, 21 Aug 2012 11:32:02 +0200	[thread overview]
Message-ID: <20120821093202.GA16089@pengutronix.de> (raw)
In-Reply-To: <d33565a509a3cf8ebb09847ce2bf114c@idefix.lespocky.dyndns.org>

Hi,

On Thu, Aug 16, 2012 at 03:06:11PM +0200, Alexander Dahl wrote:
> to not use a workaround on building our BSP I'd like to have some ideas
> on a dependency problem together with collections. We use collections to
> have slightly different builds of a BSP on the same target hardware. I
> have set PTXCONF_OPENSSL=m so I can activate/deactivate it in a
> collection. In one of our make rules (lets say rules/foo.make) there are
> the following lines:
> 
> 279 # install openssl default config
> 280 ifdef PTXCONF_OPENSSL
> 281     @$(call install_copy, foo, root, root, 0644, \
> 282         $(PTXDIST_SYSROOT_TARGET)/usr/lib/ssl/openssl.cnf,
> /usr/lib/ssl/openssl.cnf)
> 283 endif
> 
> The openssl package does not install this by default. If I had special
> needs for this file I would put it in my projectroot but I don't so the
> default which comes with openssl is sufficient.
> 
> Now my problem: If I deactivate openssl in my collection, then in
> foo.make PTXCONF_OPENSSL still seems to be defined so the install_copy
> is executed, but does not find openssl.conf if openssl it was not build
> before. Actually it was not (yet?) build in this case because nothing
> else depends on it. `ptxdist install openssl` and then `ptxdist go`
> leads to installing openssl.conf although I don't need it.
> 
> I see two possible solutions at the moment from my point of view:
> 
> 1) There's a way to test in the make file if openssl is activated in
> the collection and I missed it.

ifneq ($(filter openssl,$(PACKAGES)),)
...
endif

I think. I would not recommend this. This will break if you switch
collections without rebuilding everything.
Also, you need to depend on openssl to make sure the file is already
available.

> 2) Someone™ adapts the openssl package to make it possible to choose
> between installing the generic openssl.conf or her own copy from
> projectroot.

install_alternative should looks in pkgdir if nothing is found in
projectroot etc.

> 3) The third even more elegant solution I missed.

Create a separate package that selects openssl and is enabled/disabled with
it on the collectionconfig.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2012-08-21  9:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-16 13:06 Alexander Dahl
2012-08-21  9:32 ` Michael Olbrich [this message]
2012-08-29 12:40   ` Alexander Dahl
2012-08-30  9:29   ` Alexander Dahl
2012-09-03 15:20     ` Michael Olbrich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120821093202.GA16089@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox