Rhialto <rhialto%falu.nl@localhost> writes: > The current/old package just downloads that big distfile only because > of the sources of the emulator in it, and it ignores the bulk. It would be nice if upstream had the emulator and the OS image separately; I didn't quite follow. > However, with an emulator alone you can't do much, so it would be nice > to have a package (or the same package maybe) which installs some useful > guest operating system to use with it. I lean to separate, because I can imagine someone finding ITS to really retrocompute instead of this newfangled TOPS-20. > That doesn't seem to fit so well in our package updating strategy. Once > you use the guest OS, you change the disk image. Since the guest OS > should logically depend on the emulator, any update of the emulator > would cause a re-install. That seems rather impractical. It strikes me that the OS package should install a read-only copy of the image, and then there should be a command to instantiate an image from that copy. That avoids the issue. > There is a mechanism in pkgsrc for config files, but those are fairly > small. That is to install the upstream version as an "example" file, and > only make a copy to an etc directory if there isn't one yet. Sort of like what I said, except automated, mislabeling images as config, and basically added magic. > I'm not sure that model is useful for binary files of 475 MB. > Does anyone have some clever suggestion here? Or is is totally > unfeasable to create a package for some large "example-style" files? it probably works, but the image doens't belong in etc. Arguably the user should choose.
Attachment:
signature.asc
Description: PGP signature