Package: simple-cdd Version: 0.6.5 Followup-For: Bug #958277
> The maintainer scripts for each individual package and their debconf > templates are where to look. I recommend putting this in the docs. > I wouldn't expect the "hello" program to document the fundamentals of > computer science, or the working of electricity, or atomic theory, or > the origins of the universe... even though all of those are, ostensibly, > all relevent. I would, in the way that docs are supposed to do that. I think you don't know a lot about documentation theory. You do all of that by saying "This project requires a computer running Debian," and if people aren't sure they have that then they research Debian, and computers, and their dependencies, etc. That's just the way all documenation is always written. Anything else is just scribbles. Anyway you effectively do that in yours, so it's not material here. But it is similar to how the debian-installer doc should reference the HowTo, which should reference the README as the authoritative doc. Otherwise we're all just clicking around desperate for anything that says "simple-cdd" on it. >> Great idea! Are you aware that the README does not mention >> "debconf-get-selections" once? So it would take someone who does this >> every day to think of this excellent solution. Thank you for sharing >> this. I recommend adding it to the README, maybe the HowTo.. > > This could perhaps be briefly touched on in the simple-cdd README, and > referencing relevent chapters of the debian-installer manual. It probably belongs in the same section that the first item does about debconf templates. In a section about how to create a useful preseed file. > Yes, the README should be the authorative source for simple-cdd. Okay great. Then the HowTo and the debian-installer manual should reference that. > If you load the preseeding after the question has already been asked, > then at best, it doesn't magically travel through time an un-ask the > question... at best, it does nothing, at worst, it might trigger bugs. That makes sense but it does not relate to anything clear about how NAME.preseed works, how --preseed works, and how --auto-preseed works. Please, I've asked this every way that is possible. Please document this interplay. > an't know for sure, but sounds like it *might* be a bug in the code. > > If you could re-try with "simple-cdd --locale=en_CH --keyboard=us" with > an empty ./profiles directory and empty ./images directory (you can > probably leave ./tmp, since it sounds like you don't have much > bandwidth), that would be great. I did this, moved profiles/ and deleted images/. The new image was generated in seconds which makes me wonder if I was really doing what you want. Anyway, the result is the same. I am asked what installer to use, I choose regular "Install" and my first question is what language to use. One difference is you wrote "simple-cdd --locale=en_CH --keyboard=us" but I used "build-simple-cdd --locale=en_CH --keyboard=us" and I think that was just a typo right? Anyway I also did it your way and the result was the same. So it's looking like a bug. I will do more testing if you want, including a new images/ directory. > it sounds like you don't have much > bandwidth I wouldn't say that. But building these CDs every time I want to test a new config option is taking a toll, sure.
