From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Do ipkg-push with SHA256 checksums
Date: Thu, 9 Apr 2020 09:55:08 +0200 [thread overview]
Message-ID: <20200409075508.GA2081@pengutronix.de> (raw)
In-Reply-To: <PR1PR02MB48263349D108A127B7998C0ABFC30@PR1PR02MB4826.eurprd02.prod.outlook.com>
Hi,
On Tue, Apr 07, 2020 at 10:33:31AM +0000, Simon Falsig wrote:
> I'm trying to setup ipkg-push to repository, generating a signed Packages
> list with SHA256 checksums (using opkg, and the --checksum SHA256
> parameter). From what I can see though, the ipkg-push is done by
> scripts/ipkg-push, which doesn't have a way of setting the checksum type,
> and just calls ${TYPE}-make-index without any parameters. I can easily
> hack something together to make this work for me (by just modifying the
> ipkg-push script), but is there a more correct way?
>
> Judging from the ipkg-push file, it's made to support not just opkg, but
> also ipkg, which I don't think supports the SHA256 checksum. So just
> blindly adding the checksum parameter to the commandline would not
> maintain the generic support. On the other hand, I haven't found any
> other users of the script than ones where it's called with opkg as the
> type.
ipkg-push is pretty much unmaintained on my side. I don't use it at all.
This is the only reason why it still supports ipkg. We removed the ipkg
support pretty much everywhere else a long time ago.
I don't know much about this but it seem to me, that always having SHA256
checksums wont hurt, right?
With all that, I think:
> Suggestions:
> - Make ipkg-push just support opkg, and allow the checksumtype to be
> specified as a parameter to the script (image_ipkg.make already
> generates the local using opkg-make-index only)
This is the way to go. Just remove the 'type' option. And, unless there is
a good reason against it, just add the '--checksum SHA256' arguments
unconditionally.
Probably for the other user of opkg-make-index as well.
Michael
> - Maintain ipkg/opkg support by making some more elaborate parameters
> (for instance an "make-index-extra" that is then just passed from
> ipkg-push to ${TYPE}-make-index
> - Pull index generation out of ipkg-push, and let it be done by
> image_ipkg.make instead (which seems to be the only other place that is
> currently calling any of the -make-index functions)
> - Something entirely different
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2020-04-09 7:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 10:33 Simon Falsig
2020-04-09 7:55 ` Michael Olbrich [this message]
2020-04-15 8:40 ` Simon Falsig
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=20200409075508.GA2081@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