mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] Ptxdist lightweight packaging usecase.
Date: Wed, 20 Jan 2021 18:39:29 +0100	[thread overview]
Message-ID: <b376da73-dcbf-6a37-62ce-0cae13429e5d@t2data.com> (raw)

Hi.

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.

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.

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.

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.

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de

             reply	other threads:[~2021-01-20 17:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 17:39 Christian Melki [this message]
2021-01-21  6:38 ` Denis Osterland-Heim
2021-01-21 12:07 ` 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=b376da73-dcbf-6a37-62ce-0cae13429e5d@t2data.com \
    --to=christian.melki@t2data.com \
    --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