Re: Changing policy for the Maintainer field

[Paul Cager] > Would this still allow us to get a package overview for all of the > packages owned by the team: Yes. The summary will include all team maintained packages as long as the list is listed as maintainer or uploader. Friendly, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [E

Re: Changing policy for the Maintainer field

Marcus Better wrote: > Hi, > > I suggest we adopt the same scheme used by the Perl team [1]: > Maintainer = the main _person_ responsible for the package > Uploaders = the team mailing list + members who actually care for the > package (who have touched it in the past, for example). > Wo

Location of API docs

I am updating the BCEL library to the new upstream version. The old version installed the Javadocs into: /usr/share/doc/$package/doc/api Daniel Baumann queried this last night on IRC, and it seems that other (newer) packages (e.g. libxalan2-java-doc) install into /usr/share/doc/$package/api

Re: debian key-signing in victoria bc

Hi, Shaun Jackman said: > On 1/9/07, Alan Ezust <[EMAIL PROTECTED]> wrote: >> Ah, you maintain another java package! that's good to know. >> >> So azureus does not require java 1.5, I take it? >> I see under depends, it requires java2-runtime and >> java-virtual-machine. Those are (I think) for 1.