Originally posted by SNU
It was just an feature Idea _._
Surely its more simple to do that command and I already did. I also have just a few s-roots so it doesnt really mention.
But I thought in future it might be a nice standard that services root cant expire by default.
I don't talk about the laziness to type that 1-line command after opering up.
As you argue it means that if you order a bottle of beer in a pup and also order a beer glass to drink out of this... you might answer "you don't need a glass you still can drink it directly from the bottle". Do you understand now how I mean this feature-suggestion?
oh I wasn't arguing, and I'm sorry if you took it as such. I do fully understand your request, in short I don't think it's worth it because the trouble it takes to add this feature doesn't really equal a huge gain, and the headaches from other side effects, such as support, flexability .. etc .. of this new command would cause more time wasted in dealing with that it takes to set no expire on in the first place.
Basiclly, using your analogy, of serving beer from a glass vs from the bottle.
Think of it this way:
1> someone had to buy that glass
2> it gets washed several times a day (costing resources like soap and water).
3> every time the glass is used it could possible get broken or stolen.
4> some people will complain if we don't serve in both glasses and bottles so we must do both, which makes it more difficult.
whereas:
1> the bottle gets recycled/thrown away.
In this case you are asking us to start serving beer in glasses instead of bottles after many years of successfully selling beer in bottles and I'm saying that the headaches caused by that are not worth buying the glasses.
I hope you understand *my* point of view.
It's very easy to make this work, a well placed
|| is_services_root(u); will do. But that doesn't allow any flexability at all.
[Edited on 9-8-2007 by katsklaw]
