Re: [Cp-tools-discuss] packaging cp-tools for debian

[Grzegorz Prokopski]

W liście z wto, 13-08-2002, godz. 22:53, Brian Jones pisze: 
> Grzegorz Prokopski <address@hidden> writes:
> > Some technical questions (if you want to give me some advice):
> > - ATM I have created separate packages for cp-tools (javap, javah,
> > serialver) and separate for gjdoc. Do you think that it is right?
> > Maybe it would be better to have just one classpath-tools
> > package with ALL this stuff in it? what about automakejar then?
> > what about texinfo-doclet? should they all be in ONE package?
So... nobody would like to give ma an advice on this one?
Maybe I state it differently.
Are you going to have just ONE releaseble set off tool - I mean
you release 0.5 version which includes cp-tools, gjdoc, textlets,
automakejar?

Or will they have seaprate releases? (in the future)

It is important, because I wouldn't like to change package layout
one the package is in the distro (or even worse - after it comes
into testing and then stable).

You mentioned tools.jar that we should have. Would it consist of
what? cp-tools and gjdoc - it seems could be in that one jar
(and be release togoether, under one name-number).

> > - I needed some names for javap, javah i serialver, so I added
> > cp- prefix (cp-$origname) and put it into /usr/bin/
> > do you think it is OK?
> I believe Debian is fond of creating some weirdness in /etc and
> /usr/bin such that if you install more than one version of 'vi' for
> instance that you can configure to a particular version.  That is
> probably how these tools should be viewed as well is my guess.  On my
> system, I would rather they had the traditional names of javah, javap,
> javadoc, but these can just be shell script wrappers for whatever.
Sure we have /etc/alternatives/ symlinks, but they must _link to
somewhere_ - if you want alternatives - you need to be able to install
those "alternative" packages at the same time - so they cannot
contain the same files! (/usr/bin/javap for ex.), but instead they
have their own names for that "alternative" tool, like
/usr/bin/$sth-$mainname or /usr/lib/$sth/$mainname or
/usr/lib/$sth/bin/$mainname.
then /etc/alternatives/$mainname symlink chooses which you use.
and /usr/bin/$mainname points to /etc/alternatives/$mainname

Huh... I just wanted your advice on you would you like it best ;)

> > - oh - and I couldn't get gjdoc Makefile working, so I just
> > jikes `find . -name \*.java`
> > fastjar `find . -name \*.class`
> > Any objections?
So I assume I did it right.

Best regards

                                        Grzegorz B. Prokopski

signature.asc
Description: PGP signature