Revision history [back]

Can you just create a new workspace, clone the packages you are changing, and symlink from the other workspace any packages which depend on it? Then when you build your new workspace source the first beforehand. Then you only have to build the package your changing and its dependents.

Can you just create just:

• Create a new workspace, clone workspace
• Clone/copy and change branches for the packages you are changing, and symlink changing and
• Symlink from the other workspace any packages which depend on it? it?
• Then when you build your in a new workspace terminal source the first beforehand. Then workspace and build the second one you just constructed?

This way you only have to build the package your changing and its dependents.dependents, which you have to rebuild anyways. At least you don't have to rebuild the packages which the package you are changing depends on.

Can you just:

• Create a new workspace
• Clone/copy and change branches for the packages you are changing and
• Symlink from the other workspace any packages which depend on it?
• Then in a new terminal source the first workspace and build the second one you just constructed?

This way you only have to build the package your changing and its dependents, which you have to rebuild anyways. At least you don't have to rebuild the packages which the package you are changing depends on.

Also, if you're not using ccache (https://ccache.samba.org/), you should, that will help on repeat compiles.