symlinking or alternative workflow

I have a private repository for my project. The repository includes 2 modules, 2 themes, 1 install profile and 1 custom library of code.

Currently when I set up a platform, I run a script something like this:

#! /bin/bash

REPO=/path-to-repository
STAMP=$(date +%Y%m%d)
PLATFORM=/path-to-platform/platform-$STAMP

# Normal drush make.
drush make $REPO/path-to-makefile.make $PLATFORM

# Create additional paths not created with the make.
mkdir $PLATFORM/sites/all/libraries
mkdir $PLATFORM/sites/all/modules/custom

# Link in development paths.
ln -s $REPO/path-to-profile/my-profile $PLATFORM/profiles/my-profile
ln -s $REPO/path-to-library/my-library $PLATFORM/sites/all/libraries/my-library
ln -s $REPO/path-to-module/my-module $PLATFORM/sites/all/modules/custom/my-module
ln -s $REPO/path-to-theme/my-theme $PLATFORM/sites/all/themes/custom/my-theme

cd $PLATFORM

I'm looking to get rid of this setup script and use a native make file. This would mean that to create a platform, I can enter the make file path into Aegir directly.

I have considered putting 4+ separate git clone references into the make file. But then it seems that this is really inconvenient for development, I would have to have another script anyway for pull all the repositories, etc.

What would be great is to have an option in the make file to do things like this:

projects[my-module][link] = /path-to-repo/path-to-module

Is this something that might get into drush? Is there something already available? I've read a few issues and I have a feeling it's not considered something that drush should be able to do. In which case I'd be interested in suggestions about changes to my development workflow.

Thanks for any feedback.