[ptxdist] Ptxdist lightweight packaging usecase.

[ptxdist] Ptxdist lightweight packaging usecase.

[Christian Melki]

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

Re: [ptxdist] Ptxdist lightweight packaging usecase.

[Denis Osterland-Heim]

Hi,

I am not 100% if I got your point.

If you want to speed-up the ptxdist build you may have a look at https://www.ptxdist.org/doc/daily_work_section.html#using-pre-built-archives

If you want to create an environment for application developers where they can compile the application without ptxdist,
you just need to provide the `platform-XXX/sysroot-target` and a bunch of variables depending on the build-system.

Regards, Denis

Am Mittwoch, den 20.01.2021, 18:39 +0100 schrieb Christian Melki:
> 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
Diehl Connectivity Solutions GmbH
Geschäftsführung: Horst Leonberger
Sitz der Gesellschaft: Nürnberg - Registergericht: Amtsgericht
Nürnberg: HRB 32315

________________________________

Der Inhalt der vorstehenden E-Mail ist nicht rechtlich bindend. Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen.
Informieren Sie uns bitte, wenn Sie diese E-Mail faelschlicherweise erhalten haben. Bitte loeschen Sie in diesem Fall die Nachricht.
Jede unerlaubte Form der Reproduktion, Bekanntgabe, Aenderung, Verteilung und/oder Publikation dieser E-Mail ist strengstens untersagt.

- Informationen zum Datenschutz, insbesondere zu Ihren Rechten, erhalten Sie unter:

https://www.diehl.com/group/de/transparenz-und-informationspflichten/

The contents of the above mentioned e-mail is not legally binding. This e-mail contains confidential and/or legally protected information. Please inform us if you have received this e-mail by
mistake and delete it in such a case. Each unauthorized reproduction, disclosure, alteration, distribution and/or publication of this e-mail is strictly prohibited.

- For general information on data protection and your respective rights please visit:

https://www.diehl.com/group/en/transparency-and-information-obligations/


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

Re: [ptxdist] Ptxdist lightweight packaging usecase.

[Michael Olbrich]

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