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] Ptxdist lightweight packaging usecase.
Date: Thu, 21 Jan 2021 13:07:43 +0100	[thread overview]
Message-ID: <20210121120743.GX2915@pengutronix.de> (raw)
In-Reply-To: <b376da73-dcbf-6a37-62ce-0cae13429e5d@t2data.com>

Hi,

On Wed, Jan 20, 2021 at 06:39:29PM +0100, Christian Melki wrote:
> I'd like to package (docker) a complete ptxdist build environment for a
> target platform but as light as possible. Since most application developers
> do not care about platform stuff, but still need to build images from time
> to time.

What exactly do you want to do in the docker? Just create images? Compile
selected packages?

> So now I have this question: Can I purge build and still produce results?
> 
> If I build a platform and remove src, platform-X/build-target,
> platform-X/build-host the actual storage requirements for a docker becomes
> _far_ less. All state are kept so I'd want the user to be able to do clean
> && compile for his rules. Also I'd like to be able to do a complete go &&
> images.

If a package is done and not rebuilt, then you don't need the corresponding
directory in build-target / build-host and packages/.

> The major caveat seems to be the sources directory. If I whipe the sources,
> ptxdist tries to rebuild stuff, even if there is no file (not changed,
> missing) and all states are completed. Get, prepare, compile, install etc.

There is a dependency on the source archive. However, it's a "existence
only" dependency, so the timestamp of the file does not matter. It should
be possible to replace all the source archives with empty files.

> Is there a proper way ptxdist can accomodate this usecase? I don't find it
> unresonable. There is little point in keeping everything or every user
> producing every bit of the result.
> Storage requirements is only like 10% of the original. Far easier to keep
> complete states of releases as fast checkpoints for minor corrections.

I think, with the right tricks this should already be possible. But only
if you are very careful. As soon as some dependency triggers a rebuilt then
it will break apart with strange errors. And you'll probably need to
rebuild most of the BSP. And changing that is quite complex.

Michael

-- 
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
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

      parent reply	other threads:[~2021-01-21 12:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 17:39 Christian Melki
2021-01-21  6:38 ` Denis Osterland-Heim
2021-01-21 12:07 ` Michael Olbrich [this message]

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=20210121120743.GX2915@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