[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [platform-vcm-dev] bugzilla 24724: permission bits
|
Tom,
From a CVS plugin standpoint, the problem with native code is it will
require CVS to have specific support for one or more platforms. Currenty
the CVS support has no specific platform support requirements. Since you
have done some leg work on this, I will investigate the various options we
have with the hope of comming up with a solution for 2.1. Here's the
options as I see them:
1) Apply your patch and provide support for other platforms that either
sets the bit or does nothing (for platforms that don't have execute bits).
2) Investigate whether Platform Core would provide the natives since it is
conceivable that other plugins would want to access/set the execute bit.
3) Use Runtime#exec to get/set the execute bit when required. This would be
a bit slower than 2 but should still work.
My preference is option 2 but given that option 3 would work I suspect that
Platform Core will not opt for option 2. I do not like option 1 for the
reasons stated above but it may be possible to combine 1 and 3, having 3 as
a general solution but somehow allow fragments to provide native
implementations for improved performance. I will investigate each of these
options further and let you know what the resutls are.
Michael
Tom Tromey
<tromey@xxxxxxxxxx> To: platform-vcm-dev@xxxxxxxxxxx
Sent by: cc:
platform-vcm-dev-admin@ Subject: [platform-vcm-dev] bugzilla 24724: permission bits
eclipse.org
10/15/2002 02:59 PM
Please respond to
platform-vcm-dev
Bug 24724 is pretty important to us. We expect some of our users
(particularly those inside the company) will try Eclipse on their
favorite free software project, and immediately run into difficulty
because, e.g., `configure' will lose the executable bit on checkout.
I've implemented a fix for this bug. However, I've done it in a
fairly ad hoc way. I added a couple new native methods to
org.ecipse.team.internal.ccvs.core.util.Util -- one to fetch the
permissions of a file and another to set the permissions. Then I
found workable spots in the source to call these methods.
Is this an ok approach? I looked at putting new methods into IFile
and building a more abstract and general API for file permissions, but
that seemed like a complicated way to fix a local problem.
Are these patches interesting to you? If so, I'll upload them into
the PR.
Tom
_______________________________________________
platform-vcm-dev mailing list
platform-vcm-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-vcm-dev
