Since you're building your own fork, you could simply disable the code by adding the #ifdef at the right places. You could use git to more easily manage the merge tracking. You could also setup a continuous build but note that our buildbot code doesn't support git at the moment. http://sites.google.com/a/chromium.org/dev/developers/testing/chromium-build-infrastructure
M-A On Fri, Jul 3, 2009 at 1:33 PM, Daniel Cowx <[email protected]> wrote: > > Yeah, it would be an administrative feature for a version of Chromium > that is being developed for Library use. The library admins don't want > users to be able to download files. > > On Jul 3, 10:26 am, Peter Kasting <[email protected]> wrote: > > On Fri, Jul 3, 2009 at 10:22 AM, Daniel Cowx <[email protected]> > wrote: > > > If not, where would be the most logical place to add this > > > functionality? > > > > No, and I Don't Know, but presumably "as an extension", assuming we have > an > > API or proposed API that allows an extension to respond to queries like > > "what should the disposition of the link be". > > > > PK > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
