[OpenIndiana-discuss] Package lists

taemun taemun at gmail.com
Sun Oct 24 03:27:53 UTC 2010

Someone on Debian-testing has added rows for claws-mail and pgadmin3, and
I'm going to have to remove them.

The layout of that sheet is intentionally following that of distrowatch
(Column A is of the form "abiword (2.8.6)", which Columns B & C are
automatically updated from). The number of rows exactly matches the number
in each of the pages, eg
http://distrowatch.com/table.php?distribution=openindiana (after you hit
Refresh in the middle of the page).

If people start adding rows which don't match this format, when we try to
update automatically (ie, copy and paste columns) then it's all going to

If we're going to start a wishlist (as I presume Mr Debian was trying), this
should be on another sheet, or possibly in a Wiki page. Thoughts?

Ken Mays: whilst there is a whole bunch of software available from other
sources, I thought it would be nice to show that which is available simply
by typing "pkg install <name>".

eg, on Ubuntu you'd type apt-get install blender and get:

(Possibly a better example would have been JRE - 6u18 is avail in repo, and
6u22 from Oracle directly. I'd want to see 6u18 in the list, personally.)

Maybe that isn't the direction that Alasdair wanted this to go in. Could you

Lastly, I'd love to see some kind of alias system worked out for pkg,
whereby typing "pkg install libvorbis" can work out by itself that libvorbis
is part of the ogg_vorbis pkg, and just go get that. Having to type pkg
search libvorbis*, then work out what you want manually is a bit time
consuming. Another option would be to just split packages into their
components. If something depends upon libvorbis and libogg, both will get
downloaded, anyway. I'm not sure how package consolidation is a good thing.


On 24 October 2010 11:39, Jeppe Toustrup <openindiana at tenzer.dk> wrote:

> 2010/10/24 Alasdair Lumsden <alasdairrr at gmail.com>:
> > This is absolutely fantastic work - thanks to everyone who has
> contributed to it :)
> You're welcome...
> > The next step is to split packages into:
> >
> > 1. Packages we have but that should be updated to a newer version
> > 2. Packages we are missing, but want to add within 3 months
> > 3. Packages we are missing, but want to add within 6-12 months
> >
> > Then the rest can be considered packages that are nice to have, or not
> wanted/needed.
> I have started with making a copy of the DistroWatch sheet, and tried
> to only list server related packages on that list - since it's what I
> know most about. It mainly shows lack in mail servers (exim, postfix),
> ftp servers (proftpd, vsftpd), database servers (postgresql, firebird)
> and lastly various web based packages (pgadmin, phpmyadmin,
> wordpress).
> It would probably be a good idea to work on the network based services
> first, and then leave the webbased for now. PostgreSQL has already
> been handled, afaik, and should be available in the next version of
> OpenIndiana.
> > This will then allow us to focus on getting those packages added, and
> serve as a method of distributing the work. Guido (gber) is doing some great
> work with regards to an extras consolidation for this software to live in:
> >
> > http://wiki.openindiana.org/display/~guido/OI+Extra+Consolidation
> >
> > If anyone is interested in helping him with this please get in touch.
> I might be able to help out a bit, but it will probably mostly be in
> the triaging/testing/version bumping manner, since I don't have much C
> programming experience.
> --
> Venlig hilsen / Kind regards
> Jeppe Toustrup (aka. Tenzer)
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss

More information about the OpenIndiana-discuss mailing list