7:09 p.m.
Under what circumstances must REQUIRED be used? I have a package that
requires another package to be installed in order for it execute. I can
build the package, however, without specifying that package in REQUIRED and
if I do specify it the build fails. The build works because my PRELOAD looks
for the other package in the load-path and sets things up accordingly.
As long as the other package has been installed, I am ok.
So, do I have to bite the bullet and figure out why my build fails or can I
leave it out of REQUIRED? If REQUIRE is only for build-time issues than I am
OK. If REQUIRE is used so that the package management facility knows each
package's runtime prerequisites than I am stuck.
--
Jake Colman
Principia Partners LLC Phone: (201) 209-2467
Harborside Financial Center Fax: (201) 946-0320
902 Plaza Two E-mail: colman(a)ppllc.com
Jersey City, NJ 07311 www.principiapartners.com
8:12 p.m.
On Mon, 2003-07-21 at 21:09, Jake Colman wrote:
Under what circumstances must REQUIRED be used? I have a package
that
requires another package to be installed in order for it execute. I can
build the package, however, without specifying that package in REQUIRED and
if I do specify it the build fails. The build works because my PRELOAD looks
for the other package in the load-path and sets things up accordingly.
As long as the other package has been installed, I am ok.
To me it looks like you're using it correctly, but just to verify, you
are using REQUIRES in Makefile, not REQUIRED?
So, do I have to bite the bullet and figure out why my build fails or
can I
leave it out of REQUIRED? If REQUIRE is only for build-time issues than I am
OK. If REQUIRE is used so that the package management facility knows each
package's runtime prerequisites than I am stuck.
It's kinda both. It's really for build time dependencies, but the
package ui uses it to suggest (not enforce) installation of "dependent"
packages (see 'r' in the "List and install" view).
--
\/
8:24 p.m.
>>>> "VS" == Ville Skytt <Ville> writes:
VS> On Mon, 2003-07-21 at 21:09, Jake Colman wrote:
> Under what circumstances must REQUIRED be used? I have a package
that
> requires another package to be installed in order for it execute. I can
> build the package, however, without specifying that package in REQUIRED and
> if I do specify it the build fails. The build works because my PRELOAD looks
> for the other package in the load-path and sets things up accordingly.
> As long as the other package has been installed, I am ok.
VS> To me it looks like you're using it correctly, but just to verify, you
VS> are using REQUIRES in Makefile, not REQUIRED?
Yes, REQUIRES. Sorry, typo.
> So, do I have to bite the bullet and figure out why my build
fails or can I
> leave it out of REQUIRED? If REQUIRE is only for build-time issues than I am
> OK. If REQUIRE is used so that the package management facility knows each
> package's runtime prerequisites than I am stuck.
VS> It's kinda both. It's really for build time dependencies, but the
VS> package ui uses it to suggest (not enforce) installation of
"dependent"
VS> packages (see 'r' in the "List and install" view).
Hmmmm. My package definitely requires the other one or it cannot be used.
So, first I need REQUIRES to work so that the package GUI can make the proper
suggestion. I also need to enforce that the dependant package is actually
installed.
Oy! How do I do this? And how can I track down why I cannot compile if I
use REQUIRES?
--
Jake Colman
Principia Partners LLC Phone: (201) 209-2467
Harborside Financial Center Fax: (201) 946-0320
902 Plaza Two E-mail: colman(a)ppllc.com
Jersey City, NJ 07311 www.principiapartners.com
9:32 p.m.
On Mon, 2003-07-21 at 22:24, Jake Colman wrote:
>>>>> "VS" == Ville Skytt <Ville>
writes:
VS> On Mon, 2003-07-21 at 21:09, Jake Colman wrote:
>> Under what circumstances must REQUIRED be used? I have a package that
>> requires another package to be installed in order for it execute. I can
>> build the package, however, without specifying that package in REQUIRED and
>> if I do specify it the build fails. The build works because my PRELOAD
looks
>> for the other package in the load-path and sets things up accordingly.
>> As long as the other package has been installed, I am ok.
VS> To me it looks like you're using it correctly, but just to verify, you
VS> are using REQUIRES in Makefile, not REQUIRED?
Yes, REQUIRES. Sorry, typo.
Ok. I should have elaborated a bit, REQUIRES is used eg. to "pull in"
the auto-autoloads of required packages at build time.
>> So, do I have to bite the bullet and figure out why my
build fails or can I
>> leave it out of REQUIRED? If REQUIRE is only for build-time issues than I
am
>> OK. If REQUIRE is used so that the package management facility knows each
>> package's runtime prerequisites than I am stuck.
VS> It's kinda both. It's really for build time dependencies, but the
VS> package ui uses it to suggest (not enforce) installation of
"dependent"
VS> packages (see 'r' in the "List and install" view).
Hmmmm. My package definitely requires the other one or it cannot be used.
So, first I need REQUIRES to work so that the package GUI can make the proper
suggestion. I also need to enforce that the dependant package is actually
installed.
Oy! How do I do this? And how can I track down why I cannot compile if I
use REQUIRES?
I think REQUIRES can eventually be used, and bet there's a bug lurking
somewhere currently. Possibly one of the below, or a missing autoload
cookie in hyperbole.
Here's a couple of things to check (dirs relative to packages top dir):
- Is oo-browser listed in package-compile.el (package-directory-map)?
*** I see that hyperbole isn't; it should be. Does adding them help?
- Is oo-browser in xemacs-packages/Makefile (PACKAGES)?
Posting an URL to a tarball containing your xemacs-packages/oo-browser
dir would be helpful...
--
\/
11:11 p.m.
On Tue, 2003-07-22 at 00:56, Norbert Koch wrote:
Ville Skyttä <ville.skytta(a)iki.fi> writes:
> - Is oo-browser listed in package-compile.el (package-directory-map)?
> *** I see that hyperbole isn't; it should be. Does adding them help?
Uh, nice one. I haven't known about this, darn. Fix in a jiffy.
I knew your eagle eye would catch that :) And I'm sorry about the messy
piece-by-piece delivery of the bag'o tricks I have for packages.
Hopefully some day there is a nice bunch of written docs for this stuff.
--
\/
6:43 a.m.
Ville Skyttä <scop(a)xemacs.org> writes:
I knew your eagle eye would catch that :) And I'm sorry about
the messy
piece-by-piece delivery of the bag'o tricks I have for packages.
It's the best way to learn things :-) Now I only have to remember ...
Hopefully some day there is a nice bunch of written docs for this
stuff.
That's on top of my TODO list. I haven't been able to start it,
though:-(
norbert.
2:03 p.m.
>>>> "NK" == Norbert Koch
<viteno(a)xemacs.org> writes:
NK> Uh, nice one. I haven't known about this, darn. Fix in a jiffy.
Is it your job as release manager to update package-compile.el and commit to
cvs? Or when I introduce a new package should I be committing that change?
--
Jake Colman
Principia Partners LLC Phone: (201) 209-2467
Harborside Financial Center Fax: (201) 946-0320
902 Plaza Two E-mail: colman(a)ppllc.com
Jersey City, NJ 07311 www.principiapartners.com
2:02 p.m.
>>>> "VS" == Ville Skytt <Ville> writes:
VS> Ok. I should have elaborated a bit, REQUIRES is used eg. to "pull
in"
VS> the auto-autoloads of required packages at build time.
Yes, I was using REQUIRES. That's what triggers the problem!
> Oy! How do I do this? And how can I track down why I cannot
compile if I
> use REQUIRES?
VS> I think REQUIRES can eventually be used, and bet there's a bug lurking
VS> somewhere currently. Possibly one of the below, or a missing autoload
VS> cookie in hyperbole.
VS> Here's a couple of things to check (dirs relative to packages top dir):
VS> - Is oo-browser listed in package-compile.el (package-directory-map)?
VS> *** I see that hyperbole isn't; it should be. Does adding them help?
VS> - Is oo-browser in xemacs-packages/Makefile (PACKAGES)?
Ding, ding ding! You get the prize. I had added oo-browser to
package-compile.el and had posted to the group that hyperbole was missing.
Of course, I didn't add hyperbole to my own copy! Now that
package-compile.el has been updated with hyperbole, my package builds fine.
VS> Posting an URL to a tarball containing your xemacs-packages/oo-browser
VS> dir would be helpful...
If I continue to have support issues like this, I will make it available for
browsing. Good idea.
Who do I speak to about getting cvs commit access so that I can put the
oo-browser module under cvs control? And do I do this only after it's all
working or can I do this even if it is still a work in progress?
--
Jake Colman
Principia Partners LLC Phone: (201) 209-2467
Harborside Financial Center Fax: (201) 946-0320
902 Plaza Two E-mail: colman(a)ppllc.com
Jersey City, NJ 07311 www.principiapartners.com
2:34 p.m.
Jake Colman <colman(a)ppllc.com> writes:
Hello Jake,
Who do I speak to about getting cvs commit access so that I can put
the
oo-browser module under cvs control? And do I do this only after it's all
working or can I do this even if it is still a work in progress?
To answer this and your other question. I'm responsible for some of
the stuff. I can give you commit access (at the moment I need
Adrian's and Stephen's help, because I haven't yet done this).
You should send me a tarball of the sources to be used in an initial
import (along with vendor and start tag if possible). I import the
sources and you get commit access to the respective subtree. Future
mangling of the code is basically up to you. Sometimes, sweeps go
through all Makefiles, but changes to the code base are up to you. At
least someone should request your approval before committing anything
in your playground.
After you're confident the package builds for you, send me a heads up,
I hook it up and pre-release a first version of it. Yes, I'm
responsible for keeping package-compile.el in sync. Also, I change
the xemacs-packages/Makefile.
Stephen, you've got that wonderful welcome text. Could you send a
copy to Jake? Thanks. BTW, I've got no objection to the current
wording.
norbert.
9:08 p.m.
>>>> "Norbert" == Norbert Koch
<viteno(a)xemacs.org> writes:
Norbert> Jake Colman <colman(a)ppllc.com> writes:
Norbert> Hello Jake,
> Who do I speak to about getting cvs commit access so that I can
put the
> oo-browser module under cvs control? And do I do this only after it's all
> working or can I do this even if it is still a work in progress?
Norbert> To answer this and your other question. I'm responsible
Norbert> for some of the stuff. I can give you commit access (at
Norbert> the moment I need Adrian's and Stephen's help, because I
Norbert> haven't yet done this).
Hi Norbert, you should have ssh and sudo on SunSITE.dk.
Does it not work?
If so, let's discuss off xemacs-beta.
Hi Jake,
http://www.xemacs.org/Develop/index.html
points to
http://www.xemacs.org/Develop/cvsaccess.html
under 1., which answers your question under 3. below
http://www.xemacs.org/Develop/cvsaccess.html#committers
So, cvs-admin(a)xemacs.org, is the guy to contact :-)
Please let us know if these instructions need improvement.
Best regards,
Adrian
Norbert> You should send me a tarball of the sources to be used in
Norbert> an initial import (along with vendor and start tag if
Norbert> possible). I import the sources and you get commit
Norbert> access to the respective subtree. Future mangling of the
Norbert> code is basically up to you. Sometimes, sweeps go
Norbert> through all Makefiles, but changes to the code base are
Norbert> up to you. At least someone should request your approval
Norbert> before committing anything in your playground.
Norbert> After you're confident the package builds for you, send
Norbert> me a heads up, I hook it up and pre-release a first
Norbert> version of it. Yes, I'm responsible for keeping
Norbert> package-compile.el in sync. Also, I change the
Norbert> xemacs-packages/Makefile.
Norbert> Stephen, you've got that wonderful welcome text. Could
Norbert> you send a copy to Jake? Thanks. BTW, I've got no
Norbert> objection to the current wording.
Norbert> norbert.
--
Adrian Aichner
mailto:adrian＠xemacs.org
http://www.xemacs.org/
7577
days inactive
7578
days old
10 comments
5 participants
participants (5)
-
Adrian Aichner -
Jake Colman -
Norbert Koch -
Ville Skyttä -
Ville Skyttä