On Wed, Aug 27, 2008 at 5:39 AM, Caius Durling <[EMAIL PROTECTED]> wrote:
> > On Wed, Aug 27, 2008 at 2:42 AM, Chris Meller <[EMAIL PROTECTED]> > wrote: > > > > > > On Tue, Aug 26, 2008 at 6:45 PM, Caius Durling <[EMAIL PROTECTED]> wrote: > >> > >> On Tue, Aug 26, 2008 at 11:36 PM, Christian Mohn <[EMAIL PROTECTED]> > wrote: > >> > > >> > My current vote is to grab whatever we are using from the "original" > >> > blueprint and put it into our admin.css. Then remove the external > >> > dependency. > >> > >> +1 > >> > >> Doing it this way we still aren't re-inventing the wheel, but we > >> aren't dependant on their svn staying stable, etc. > > > > We are, however, taking the wheel apart and using 3 of the spokes to > build > > our own wheel. > > > > If we're going to include something from an external provider, include it > > outright. Don't piecemeal it together. Not only is it error prone (both > for > > the person slicing it up and those coming later trying to figure out > exactly > > what's still included), but it's also inefficient for us to slice off > huge > > chunks and stick the rest in our file. > > > > If we can't svn:externals it, export the release and import it into our > svn. > > Don't obfuscate it. > > I thought this was what christian was meaning, I didn't mean slice the > bits out we need -- that way lies pain and disaster as they used to > say. Oh good, then we're in agreement except for the Norwegian... --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
