Hi Paolo, On Fri, Jul 12, 2013 at 05:50:55PM +0200, Paolo Cavallini wrote: > > It means that all packages you regard as relevant for GIS are injected > > into the appropriate task. The "Links" section on the left contains a > > link to the Debian GIS tasks page you most probably want to visit if you > > have no idea what tasks might mean. > > Sorry, I'm not getting your point: e.g. QGIS is marked as Up to date, whereas > its > version in deb is considerably older than the latest released.
Well, that's by design of the packages thermometer as it used to be. If you look at [1] which I used as model it reflects the same because it just compares between Debian stable and Debian unstable and sop it is rather faking a feature that upnstable is behind upstream than an issue. However, I *perfectly* agree with you that this is not a good idea and the good news is that with the current technique we can easily query for upstream version and compare against this. If nobody insists I will update the thermometer with an 'upstream' column and I would like you to propose a color / naming sheme how to mark a row if Debian is behind upstream. I even might imagine just to mark the field with the upstream version in read if it is newer than unstable. > > $ apt-cache search rgdal > > > > does not find anything and as I explained in my previous mail you need > > to inject some preliminary packaging stuff into Debian GIS VCS to create > > an entry inside the thermometer. I can not find any such stuff - please > > correct me if I'm wrong. If my explanation how things are working was > > not precise enough please be patient with me and ask for clarification > > what exactly you did not understand. > > OK, I understand. So what is the best way to suggest the inclusion of a > package? > The list at http://wiki.debian.org/DebianGis/PackageList looks oldish, and > partly > duplicates the thermometer. In Debian Med I made the experience that Wikis *always* become oldish / outdated - despite the claim what fans of Wikis will always tell you. The problem of *this* kind of Wikis is that they are usually some (overworked) one-man-Wikis - which is just in contrast to the Wiki concept. Once I realised this I invented the Blends tasks pages that are updating automatically. Thus I'm always trying to convince people to create automatically upgradable data - which for instance is to commit something to VCS. If you are serious about a package you will do it. If you just put it on a Wiki page and nobody reads this page you can even save your time to put it on the page. > > Moreover, if you want me to inject an additional package you need to > > specify to what task. BTW, when thinking about this I might add an > > additional column in the end of the table mentioning the task(s) a > > package is part of. What do you think? > > +1 > thanks. OK. I'll try to implement two new columns: upstream + tasks. I hope to get it read in about 2-3 days. Thanks for your feedback Andreas. [1] http://pkg-grass.alioth.debian.org/debiangis-status.html -- http://fam-tille.de -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
