Software installation is a rich source of troubles: how do we keep from clobbering other software? How do we find dependencies? How do we upgrade without breaking things? How do we handle incompatible versions? How do we deal with the multitude of build systems used by various packages? Many packaging systems have been developed that solve some of these problems, but they typically leave some significant problems entirely unsolved, or they solve problems downstream - where the effort must be duplicated by others - instead of upstream, where the benefit can be shared by all. The slashpackage system, for Unix-style OSes, takes a new approach by relying heavily on the filesystem to make packages both more easily accessible and more safely insulated from each other. I will cover its design features, show how to use it effectively, and address the most common objections.