Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#2 delivery tree should be computable

closed-fixed
nobody
None
5
2004-06-06
2002-07-24
Anonymous
No

Right now, you have to know in advance what the
delivery target
is going to be to know where to find the objects to
install. This makes
it really hard to port the package to new
architectures; you have to
hardcode all the other directories under src/ and say
"whatever we
don't know about must be the install tree".

If you named it after the output of 'arch' (on linux,
anyhow), that
would be ideal; then I could just install the contents of
src/linux-`arch` into my package. I don't recall how
this works for
hpux

-=Eric Schwartz

Discussion

  • Logged In: YES
    user_id=558029

    Eric:

    We put Judy in open source in a hurry, (before HP changed its mind)
    Any and all suggestions on how Judy should be packaged
    will be appreciated. I am working on getting it into the CVS
    tree right now. I obviously have a lot of things to learn. Any
    help will be appreciated.

    Doug Baskins
    doug@sourcejudy.com

     
    • status: open --> pending-accepted
     
  • Logged In: YES
    user_id=558029

    I can identify with your frustration -- I would be pissed.
    I /we are presently
    working on the problem. We put Judy in open source very
    quickly and did a
    very poor job of it. It had to be done quickly or possibly
    loose the opportunity.

    I/we are working on using the autoconf, automake, and
    libtool to make Judy
    portable across a broad range of platforms.

     
    • status: pending-accepted --> open-accepted
     
    • status: open-accepted --> pending-accepted
     
    • status: pending-accepted --> open-accepted
     
  • Logged In: YES
    user_id=558029

    Eric:
    Take a look at version 0.1.7 available at
    <http://judy.sourceforge.net/downloads>. Please comment on that
    version.

    Doug

     
    • status: open-accepted --> closed-fixed