Thanks for pointing out the page with the python sample. I see what you're referring to. In the sample, a 'workspace' is set. Because of this, you can make everything within the script relative (what you're seeing inside the tool syntax). So when the tool is run, it puts the two pieces together.
env.workspace = "C:/ResultFiles"
arcpy.PackageResult_management(rlts, 'all_layers.gpk', "PRESERVE", "CONVERT_ARCSDE", "#", "ALL", "ALL", "DESKTOP", r"C:\docs\readme.txt", "Summary text", "Tag1; tag2; tag3"
I understand your concerns about the option to enable Runtime. This decision was made as the great majority of people *would not* be creating geoprocessing packages for the Runtime. The Runtime supports a subset of the core tools in ArcGIS. I'm sure you can imagine the confusion for someone who doesn't know the Runtime wanting to "support more" with their package, only to be told the tools they're using wont work. Thats why we "hide" it, unless you understand what it does and why you'd want to use it. I'll try to get a couple lines into the geoprocessing package help which explain how to get the checkbox enabled in the package creator. The cut/paste you have below. I've since updated the text and will be available in the release after Beta2 (I missed the boat for beta2).