Trying to export to new library WITHOUT consolidating masters

Question

I am trying to export a project as a new library and I DO NOT want the masters to be included.
But when I export->project as new library and then UNCHECK "consolidate masters into new library" the raw files are still copied over, making the new library very large so I am unable to put it in Dropbox.
The original library is managed. This seems like a bug, since exporting with or without the consolidate option checked makes a library of the same size with the raw files in both.
Is there something I'm doing wrong?

Answer 1

So, the controlling issue here is 'referenced' vs 'managed' Masters. From the manual:
"If your project contains referenced images and you want the master files available to the new Aperture system: Select the “Consolidate masters into exported project” checkbox to copy the original master image files into the new library file."
It doesn't say explicitly, but implies, that unchecking that checkbox allows you to make a new library file without copying the original image files into the new library file. This is in fact how it works in my testing.
Notice it only mentions referenced images. What it doesn't say, but is in fact the case, is that if the images are 'managed' i.e., contained in the library package file, then selecting "Consolidate master into exported project" makes no difference. The original master image files get copied into the new library file whether you want them to or not. This is what happens when I test.
I've confirmed the difference between the two scenarios by selecting my project, going to File, "relocate masters for project...." and moving my master RAW's out of the library and into a folder elsewhere. After doing this, I again select the project, choose "export -> Project as New Library" and it works as expected: I can deselect the "Consolidate..." option and a library is made WITHOUT the Master Raws.
So apparently this behavior when masters are 'managed' is not a bug, it's designed to be that way. This makes no sense whatsoever.
1. Why have the checkbox for consolidating if it doesn't do anything?
2. Why NOT let you create a new library file WITHOUT copying the original master image files, JUST AS YOU ARE ALLOWED TO DO WHEN YOUR MASTER FILES ARE REFERENCED outside the original library?
So the solution is: Do not ever use Managed files. I would have thought that there would be some benefit to having the files stored in the aperture library, but apparently there are actually LESS features available. (All my RAWs are in their own file structure on my RAID in my tower and therefore referenced, but I assumed that it would be easier to just have them be managed on my laptop.)
Always use referenced files on every system and I am then able to transfer projects back and forth between systems without being forced to include the large RAWs.
Thanks for all the input, and if anyone has any insight into whether my conclusions are correct or why this might be so, I'd be grateful to hear it.