> What you have to convince me of now is: > > Why does sbuild need to change because of design choices that you made in your > scripts and why should not your scripts change to accommodate for the sbuild > behaviour?
Well, as I said, I have three different logs for each build, the build log being just one of them, and I'd like them to use the same timestamp, even if I'm not using the timestamp as an "id" yet. This is the main reason and you can forget about everything else if you like. To use the same timestamp in three different logs I had basically two choices: (1) Let sbuild to generate the build log filename with whatever timestamp scheme is hardcoded in it and rename it later. This is what you would call "accomodating for sbuild behaviour". (2) Tell sbuild explicitly the timestamp and filename I want to be used for the log timestamp from the beginning. Not really sure if it's a "design choice" or a "personal preference", but the idea of using a random (i.e. not chosen) filename just to rename it later seems odd and not elegant to me, so I am already doing (2). Everythink I ask is a way to tell sbuild "please use this timestamp I provide in this environment variable instead of generating a new timestamp", and this may be done easily with a very small patch that will not affect anybody else unless they define a certain environment variable. So, I will not try to convince you that sbuild "needs" to be changed because after all this is a wishlist bug. I would instead like to think of this in terms of "useful feature" or "not useful feature". For me, it would be definitely a useful feature, because I would not have to patch sbuild every time anymore. Thanks.
