On Fri, May 11, 2007 at 21:14:36 +0200, Nils Kneuper <[EMAIL PROTECTED]> wrote: > Bruno Wolff III schrieb: > > I have thought of something else that might be nice to do after each > > campaign is in its own directory. If references were only allowed within > > a campaign or to main line stuff and not cross campaign, we could make sure > > that removing a campaign will not break another campaign because of > > dependencies. This could enforce the rule that you are supposed to copy > > non main line objects rather than make references to them. > > > Ehm, we are already using this policy. It will be enforced for all new > content to add mainline and it is eg needed for the split debian > packages. So in this matter it does not make a real difference, since we > already do handle things this way.
I knew we had a policy of that is how things are supposed to work. What I was suggesting was that this policy be enforced in code. It might be that there is a relatively new feature doing this. I know Eric has been doing all sorts of clean up checks and of his tools may catch campaigns that do this when they are run, but that isn't the same as having wesnoth do it. Having the check in wesnoth will let campaign developers notice the problem before they try to submit their campaign (or changes to an existing campaign). _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
