> For the complete documentation index, see [llms.txt](https://docs.libnova.com/labdrive/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.libnova.com/labdrive/data-curation-and-preservation-1/preservation-activities/adding-representation-information/other-representation-information/software-as-part-of-the-rin/preserving-complex-software.md). # Preserving complex software Complex software will consist of many separate elements specifying for example: * source code * configuration * build processes * distribution between computers * control processes and frameworks * test suites In principle each element may be preserved as pieces of simple software, text files, etc. Even whole operating systems, particularly open source ones like the [Linux kernel](https://www.kernel.org/), can be built from such files, boot-strapping from a small core. It is important to understand what these core tools are in order to build the software and to be able to recognise when it is becoming impractical to re-build nd run the software. However, in some cases the software may be encapsulated in one of many ways including: * [Jupyter Notebooks](/labdrive/get-started/jupyter-notebooks.md) * [Docker and other containers as Other RepInfo](/labdrive/data-curation-and-preservation-1/preservation-activities/adding-representation-information/other-representation-information/software-as-part-of-the-rin/preserving-complex-software/emulation-virtualisation/containers-dockers.md) * [Virtual machines as Other RepInfo](/labdrive/data-curation-and-preservation-1/preservation-activities/adding-representation-information/other-representation-information/software-as-part-of-the-rin/preserving-complex-software/emulation-virtualisation/method-3-emulation-i.e.-true-emulation-virtualization-and-containerization.md) Preserving these and other more complex software is discussed in [Emulation/Virtualisation](/labdrive/data-curation-and-preservation-1/preservation-activities/adding-representation-information/other-representation-information/software-as-part-of-the-rin/preserving-complex-software/emulation-virtualisation.md). Supplementing these tools are such as [Use of ReproZip](/labdrive/data-curation-and-preservation-1/preservation-activities/adding-representation-information/other-representation-information/software-as-part-of-the-rin/preserving-complex-software/method-4-migration-1.md). An important aspect of this is that once the problem of preserving these encapsulations, in particular the RINs that are needed, then, because they are so widely used, the RINs an be re-used. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.libnova.com/labdrive/data-curation-and-preservation-1/preservation-activities/adding-representation-information/other-representation-information/software-as-part-of-the-rin/preserving-complex-software.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.