The hack to extract all RPMs should be able to work for you but I wanted to
point this out because it's saved me a few times I really needed root.
Do you have sudo access?
If so try sudo -s, if that's blocked try sudo /bin/bash (or whatever your
shell is) if that is also blocked you can always
On 10/27/05 6:27 AM, Stephan Schaefer [EMAIL PROTECTED] wrote:
Daniel Aleksandersen wrote:
Regular users don't need this window. Therefor I wrote a little
AppleScript witch disables the black window and I though that this was
something that a lot of other Mac-users could use too!
On 4/5/05 8:38 AM, Joerg Barfurth [EMAIL PROTECTED] wrote:
deleted
You can restrict access to individual settings by providing a
configuration data (.xcu) file and using the protection attributes
(oor:finalized and oor:mandatory) in that file to mark individual
settings or entire
You have some similar options on WIndows if you wrap things together into a
plugin. There are a number of libraries out there that would give you the
pieces to need to put this functionality together much easier then pulling
OOo's code apart to adapt it for Mozilla.
A related note, I've printed
I wanted to see if anyone had any input on this. I've seen some good data on
how to make a custom schema for configuration data for my component but no
way to restrict access to it.
I'm implementing some custom configuration properties for my component that
should only be changed by
These are a couple of tough ones I haven't been able to crack. I've tried to
do both as an Addon.xcu through a component and directly through BASIC (as
prototype, ending in Java) but I haven't had any luck.
I'm trying to add a command programmatically on startup with a Job addon to
the File menu.
I've looked at a number of examples that dispatch URLs into Ooo but I seem
to be missing a piece I need to do what I want to do. I have a feeling I'm
missing some interface relationships.
I have a component which is a protocol handler that currently has an
XComponentContext so I can get a number
that and things started
working.
- Brian
On 3/25/05 7:02 AM, Brian Raymond [EMAIL PROTECTED] wrote:
I've looked at a number of examples that dispatch URLs into Ooo but I seem
to be missing a piece I need to do what I want to do. I have a feeling I'm
missing some interface relationships.
I have
Juergen,
Thanks for the help, I'll keep an eye out for those.
In the meantime I got my script working. It turns out it should have been
working all along but I had a single line of white space in the manifest.xml
I have Ant dynamically build. Unopkg.exe would succeed in adding the
package to Ooo
