mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Markus Wolters" <MarkusWolters@gmx.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] How to add opkg/ipkg post install scripts to package?
Date: Fri, 20 Sep 2013 10:54:41 +0200 (CEST)	[thread overview]
Message-ID: <trinity-12b3a5fc-2773-4e26-9131-475f2817417c-1379667280941@3capp-gmx-bs23> (raw)
In-Reply-To: <20130916082345.GF14466@pengutronix.de>

Hello Michael,

the control tar ball only consists of a single control text file. Do you know any tools or ways to find out, why the rules/mypackage.postinst file is not build in?

Regards 
Markus



> Gesendet: Montag, 16. September 2013 um 10:23 Uhr
> Von: "Michael Olbrich" <m.olbrich@pengutronix.de>
> An: ptxdist@pengutronix.de
> Betreff: Re: [ptxdist] How to add opkg/ipkg post install scripts to package?
>
> Hi,
> 
> On Mon, Sep 16, 2013 at 08:57:36AM +0200, Markus Wolters wrote:
> > unfortunately I'm not able to get it work. My foo.postinst only contains an
> > echo "something" and exit 0. Rights are rx for everyone. If I extract the files
> > from ipk, there is no postinst file included and no script gets executed on
> > install/upgrade. Any ideas what's going wrong?
> 
> Take a closer look at the ipkg. It is a zip file that contains 2 tar-balls.
> The postinst script should be in the control tar-ball.
> 
> 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
> 

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2013-09-20  8:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11  6:55 Markus Wolters
2013-09-11  8:33 ` Michael Olbrich
2013-09-11  9:16   ` Markus Wolters
2013-09-11 10:34     ` Schenk, Gavin
2013-09-16  6:57       ` Markus Wolters
2013-09-16  8:23         ` Michael Olbrich
2013-09-16  8:36           ` Markus Wolters
2013-09-16  8:48             ` Jürgen Beisert
2013-09-16 12:03             ` Markus Wolters
2013-09-24  8:01               ` Markus Wolters
2013-09-24  8:08                 ` Jürgen Beisert
2013-09-25  6:09                   ` Prajwal Chandrappa
2013-09-24  8:16                 ` Markus Wolters
2013-09-24  8:28                   ` Thomas Heller
2013-09-20  8:54           ` Markus Wolters [this message]
2013-09-11 13:11     ` Marc Kleine-Budde

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=trinity-12b3a5fc-2773-4e26-9131-475f2817417c-1379667280941@3capp-gmx-bs23 \
    --to=markuswolters@gmx.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