Re: Shipping one time migration scripts with SCons
Vasily <[email protected]>
| Newsgroups | gmane.comp.programming.tools.scons.devel |
|---|---|
| Message-ID | <CABiDpknZ3iZ2PXYi9B3580NJ3ohF_hBZw4GwR_HUkQp_y-98ug@mail.gmail.com> |
Maybe such scripts could be kept in a separate directory or even in a separate repository to not be mixed with core scons code? Thanks, Vasily 02 февр. 2016 г. 0:57 пользователь "William Blevins" <[email protected]> написал: > > > On Mon, Feb 1, 2016 at 9:13 PM, Dirk Bächle <[email protected]> wrote: > >> Hi Anatoly, >> >> On 01.02.2016 20:14, anatoly techtonik wrote: >> >>> Hi, >>> >>> There is an interesting thread, which needs some >>> consensus. >>> >>> https://bitbucket.org/scons/scons/pull-requests/302/change-the-cache-to-use-2-character/ >>> >>> >> "consensus" between whom? And what is your concrete idea about how this >> consensus should be reached? It looks to me as if the issue has been >> properly discussed among the people that are actively working on the pull >> request...and they've reached a consensus already. >> One that I support too, I might add... > > > I think that a script of this nature should be revision controlled with > the software release that it is related to. I'm not sure when this script > should be removed sadly. I wish I could recommend doing it in the commit > immediately after the first SCons release containing the change, but seems > that many SCons users don't really keep up-to-date, so there is a definite > possibility for people skipping versions of the software. > > >> >> >> I am against shipping global scripts that are not >>> generally useful to all scons users, but it seems >>> that nobody agrees. >>> >>> >> Yes, I see that you have concerns and your position is on the one side of >> the scale. But the guys that have done all the hard work have a position >> too, which happens to be different from yours (=other side of the scale). >> This happens, please don't take offense over it and get upset. >> >> Best regards, >> >> Dirk >> >> >> _______________________________________________ >> Scons-dev mailing list >> [email protected] >> https://pairlist2.pair.net/mailman/listinfo/scons-dev >> > > > _______________________________________________ > Scons-dev mailing list > [email protected] > https://pairlist2.pair.net/mailman/listinfo/scons-dev > > _______________________________________________ Scons-dev mailing list [email protected] https://pairlist2.pair.net/mailman/listinfo/scons-dev