Return to Answer

I once wrote a script to solve a similar problem -- I called it "distribute" (you can read the main code of the script or the file with the help message, or download it as a package); from its description:

distribute -- Distribute a collection of packages on multiple CDs (especially good for future use with APT)

Description: `distribute' program makes doing the tasks related to creating a CD set for distribution of a collection of packages easier. The tasks include: laying out the CDs filesystem (splitting the large amount of packages into several discs etc.), preparing the collection for use by APT (indexing), creating ISO images and recording the discs.

Periodical updates to the initially distributed collection can be issued with help of `distribute'.

It does the whole process in several stages: at one stage, it creates the furure disk "layouts" by using symlinks to the original files -- so you can intervene and change the future disk trees.

The details about its usage can be read in the help message printed by the script (or by looking into the source code).

It was written with a more trickier use case in mind (issuing updates as a "diff"--the set of added new files--to the originally recorded collection of files), so it includes one extra initial stage, namely, "fixing" the current state of the collection of files (for simplicity, it does this by replicating the original collection of files by means of symlinks, in a special working place for saving the states of the collection; then, some time in the future, it will be able to create a diff between a future current state of the collection of files and the current current state). So, although you might not need this feature, you can't skip this initial stage, AFAIR.

Also, I'm not sure now (I wrote it quite a few years ago) whether it treats complex trees well, or it is supposed to split only plain (one level) directories of files. (Please look into the help message or the source code to be sure; I'll look this up, too, a bit later, when I'll have some time.)

The APT-related stuff is optional, so don't pay attention that it can prepare package collections to be used by APT if you don't need this.

If you get interested, of course, feel free to rewrite it to your needs or suggest improvements.

(Please pay attention that the package includes additional useful patches not applied in the presented code listing at the Git repo linked above!)

I once wrote a script to solve a similar problem -- I called it "distribute" (you can read the main code of the script or the file with the help message, or download it as a package); from its description:

distribute -- Distribute a collection of packages on multiple CDs (especially good for future use with APT)

Description: `distribute' program makes doing the tasks related to creating a CD set for distribution of a collection of packages easier. The tasks include: laying out the CDs filesystem (splitting the large amount of packages into several discs etc.), preparing the collection for use by APT (indexing), creating ISO images and recording the discs.

Periodical updates to the initially distributed collection can be issued with help of `distribute'.

It does the whole process in several stages: at one stage, it creates the furure disk "layouts" by using symlinks to the original files -- so you can intervene and change the future disk trees.

The details about its usage can be read in the help message printed by the script (or by looking into the source code).

It was written with a more trickier use case in mind (issuing updates as a "diff"--the set of added new files--to the originally recorded collection of files), so it includes one extra initial stage, namely, "fixing" the current state of the collection of files (for simplicity, it does this by replicating the original collection of files by means of symlinks, in a special working place for saving the states of the collection; then, some time in the future, it will be able to create a diff between a future current state of the collection of files and this saved state). So, although you might not need this feature, you can't skip this initial stage, AFAIR.

Also, I'm not sure now (I wrote it quite a few years ago) whether it treats complex trees well, or it is supposed to split only plain (one level) directories of files. (Please look into the help message or the source code to be sure; I'll look this up, too, a bit later, when I'll have some time.)

The APT-related stuff is optional, so don't pay attention that it can prepare package collections to be used by APT if you don't need this.

If you get interested, of course, feel free to rewrite it to your needs or suggest improvements.

(Please pay attention that the package includes additional useful patches not applied in the presented code listing at the Git repo linked above!)

I once wrote a script to solve a similar problem -- I called it "distribute" (you can read the main code of the script or the file with the help message, or download it as a package); from its description:

distribute -- Distribute a collection of packages on multiple CDs (especially good for future use with APT)

Description: `distribute' program makes doing the tasks related to creating a CD set for distribution of a collection of packages easier. The tasks include: laying out the CDs filesystem (splitting the large amount of packages into several discs etc.), preparing the collection for use by APT (indexing), creating ISO images and recording the discs.

Periodical updates to the initially distributed collection can be issued with help of `distribute'.

It does the whole process in several stages (at one stage, it creates the furure disk "layouts" by using symlinks to the original files -- so you can intervene and change the future disk trees).

The details about its usage can be read in the help message printed by the script (or by looking into the source code).

It was written with a more trickier use case in mind (issuing updates as a "diff" to the originally recorded collection of files), so it includes one extra initial stage, namely, "fixing" the current state of the collection of files (for simplicity, it does this by replicating the original collection of files by means of symlinks, in a special working place for saving the states of the collection; then, some time in the future, it will be able to create a diff between a future current state of the collection of files and the current current state). So, although you might not need this feature, you can't skip this initial stage, AFAIR.

Also, I'm not sure now (I wrote it quite a few years ago) whether it treats complex trees well, or it is supposed to split only plain (one level) directories of files. (Please look into the help message or the source code to be sure; I'll look this up, too, a bit later, when I'll have some time.)

The APT-related stuff is optional, so don't pay attention that it can prepare package collections to be used by APT if you don't need this.

If you get interested, of course, feel free to rewrite it to your needs or suggest improvements.

(Please pay attention that the package includes additional useful patches not applied in the presented code listing at the Git repo linked above!)

I once wrote a script to solve a similar problem -- I called it "distribute" (you can read the main code of the script or the file with the help message, or download it as a package); from its description:

distribute -- Distribute a collection of packages on multiple CDs (especially good for future use with APT)

Description: `distribute' program makes doing the tasks related to creating a CD set for distribution of a collection of packages easier. The tasks include: laying out the CDs filesystem (splitting the large amount of packages into several discs etc.), preparing the collection for use by APT (indexing), creating ISO images and recording the discs.

Periodical updates to the initially distributed collection can be issued with help of `distribute'.

It does the whole process in several stages: at one stage, it creates the furure disk "layouts" by using symlinks to the original files -- so you can intervene and change the future disk trees.

The details about its usage can be read in the help message printed by the script (or by looking into the source code).

It was written with a more trickier use case in mind (issuing updates as a "diff"--the set of added new files--to the originally recorded collection of files), so it includes one extra initial stage, namely, "fixing" the current state of the collection of files (for simplicity, it does this by replicating the original collection of files by means of symlinks, in a special working place for saving the states of the collection; then, some time in the future, it will be able to create a diff between a future current state of the collection of files and the current current state). So, although you might not need this feature, you can't skip this initial stage, AFAIR.

Also, I'm not sure now (I wrote it quite a few years ago) whether it treats complex trees well, or it is supposed to split only plain (one level) directories of files. (Please look into the help message or the source code to be sure; I'll look this up, too, a bit later, when I'll have some time.)

The APT-related stuff is optional, so don't pay attention that it can prepare package collections to be used by APT if you don't need this.

If you get interested, of course, feel free to rewrite it to your needs or suggest improvements.

(Please pay attention that the package includes additional useful patches not applied in the presented code listing at the Git repo linked above!)

I once wrote a script to solve a similar problem -- I called it "distribute" (download); from its description:

distribute -- Distribute a collection of packages on multiple CDs (especially good for future use with APT)

Description: `distribute' program makes doing the tasks related to creating a CD set for distribution of a collection of packages easier. The tasks include: laying out the CDs filesystem (splitting the large amount of packages into several discs etc.), preparing the collection for use by APT (indexing), creating ISO images and recording the discs.

Periodical updates to the initially distributed collection can be issued with help of `distribute'.

It does the whole process in several stages (at one stage, it creates the furure disk "layouts" by using symlinks to the original files -- so you can intervene and change the future disk trees).

The details about its usage can be read in the help message printed by the script (or by looking into the source code).

It was written with a more trickier use case in mind (issuing updates as a "diff" to the originally recorded collection of files), so it includes one extra initial stage, namely, "fixing" the current state of the collection of files (for simplicity, it does this by replicating the original collection of files by means of symlinks, in a special working place for saving the states of the collection; then, some time in the future, it will be able to create a diff between a future current state of the collection of files and the current current state). So, although you might not need this feature, you can't skip this initial stage, AFAIR.

Also, I'm not sure now (I wrote it quite a few years ago) whether it treats complex trees well, or it is supposed to split only plain (one level) directories of files. (Please look into the help message or the source code to be sure; I'll look this up, too, a bit later, when I'll have some time.)

The APT-related stuff is optional, so don't pay attention that it can prepare package collections to be used by APT if you don't need this.

If you get interested, of course, feel free to rewrite it to your needs or suggest improvements.

I once wrote a script to solve a similar problem -- I called it "distribute" (you can read the main code of the script or the file with the help message, or download it as a package); from its description:

distribute -- Distribute a collection of packages on multiple CDs (especially good for future use with APT)

Description: `distribute' program makes doing the tasks related to creating a CD set for distribution of a collection of packages easier. The tasks include: laying out the CDs filesystem (splitting the large amount of packages into several discs etc.), preparing the collection for use by APT (indexing), creating ISO images and recording the discs.

Periodical updates to the initially distributed collection can be issued with help of `distribute'.

It does the whole process in several stages (at one stage, it creates the furure disk "layouts" by using symlinks to the original files -- so you can intervene and change the future disk trees).

The details about its usage can be read in the help message printed by the script (or by looking into the source code).

It was written with a more trickier use case in mind (issuing updates as a "diff" to the originally recorded collection of files), so it includes one extra initial stage, namely, "fixing" the current state of the collection of files (for simplicity, it does this by replicating the original collection of files by means of symlinks, in a special working place for saving the states of the collection; then, some time in the future, it will be able to create a diff between a future current state of the collection of files and the current current state). So, although you might not need this feature, you can't skip this initial stage, AFAIR.

Also, I'm not sure now (I wrote it quite a few years ago) whether it treats complex trees well, or it is supposed to split only plain (one level) directories of files. (Please look into the help message or the source code to be sure; I'll look this up, too, a bit later, when I'll have some time.)

The APT-related stuff is optional, so don't pay attention that it can prepare package collections to be used by APT if you don't need this.

If you get interested, of course, feel free to rewrite it to your needs or suggest improvements.

(Please pay attention that the package includes additional useful patches not applied in the presented code listing at the Git repo linked above!)