Backports Repository Index - add relevant discussion thread

redcollective · 2016-02-10 23:07:37

A suggestion to aid users browsing the backports Repository Index:

https://pkg.bunsenlabs.org/repoidx.html … -backports

- A useful addition might be a link or links to relevant bunsenlabs forum posts discussing the backports - so a user can better assess why a specific backport exists?

Thanks for listening.

red

hhh · 2016-02-11 01:57:30

^Agreed, we should have a dedicated suggestion/discussion sticky for backports. Recommending that this waits until after the rc2 release, though.

Sector11 · 2016-02-11 02:42:02

Blank page.

nobody · 2016-02-11 02:51:40

Sector11 wrote:

Blank page.

Server performance has tanked. Wait & reload.

Sector11 · 2016-02-11 03:12:57

OK...

nobody · 2016-02-11 03:18:06

…you also need JavaScript, Iceweasel/Firefox>=38 or Chromium>=48 with experimental JS features enabled.

ohnonot · 2016-02-11 06:07:18

nobody wrote:

…you also need Iceweasel/Firefox>=38 or Chromium>=48 with experimental JS features enabled.

why?

damo · 2016-02-11 06:30:38

^ Probably because @nobody had more important things to do at the time than write code to be useable in all browsers and versions.

Read the page source - the comments are informative and amusing

nobody · 2016-02-11 07:27:47

ohnonot wrote:

nobody wrote:
…you also need Iceweasel/Firefox>=38 or Chromium>=48 with experimental JS features enabled.
why?

I wrote the script against Firefox just to find out that features I thought were cool (ES6 features) are too cool for Google so they chose not to implement them ASAP (related mostly to for..of iteration over Map()s I think).

That's what you get when you start with an idiotic toy language, slap some kit on top of it while talking to everybody else who is also busy slapping their own kits on top of it, and taking some pieces of kit from the guys left and right. For example Lua is probably (unverified claim) now about 1% the size of a standard JS implementation (excluding libraries like browser APIs) and syntax-wise does everything JS can do, including objects and inheritance, first-class functions, COMPLETELY CUSTOMIZABLE grammar either via the debug library or C libraries, and most importantly, somehow its developers thought it would make sense to be able to iterate over the keys and values of an object at the same time and to have proper scoping to begin with ('var' anybody?).

Most of the unportability of bl-repo-index.js is due to my own ignorance about the JS ecosystem ('hey how about writing this in JS instead of $real_programming_language, I could learn something while doing it'), but I shouldn't have to worry about crap like the above and to use a compatibility matrix of some sort spanning 40 colums and 9000 rows. BTW the document I linked is supposed to reflect what JS people call The Standard, but as you can see, no implementation is nowhere near 100% coverage of everything.

Side note: Lady IRIS (Improved Repository Index System), based on python-bottle, has been in the works for some time now but I don't know whether I will use or release it at some point due to the lack of time, and priorities (I like working on forecast so much more) and/or inclination. bl-repo-index works, for the most part.

nobody · 2016-02-11 07:44:56

redcollective wrote:

A suggestion to aid users browsing the backports Repository Index:
https://pkg.bunsenlabs.org/repoidx.html … -backports
- A useful addition might be a link or links to relevant bunsenlabs forum posts discussing the backports - so a user can better assess why a specific backport exists?
Thanks for listening.
red

Hm, the index is generated just from the Packages file in the repository so the information would need to be added and maintained manually.

How about explaining/linking on pkg's landing page instead?

ohnonot · 2016-02-11 21:17:19

nobody, thanks for the explanation.
first of all, i slap myself for asking one-word-questions, one just shouldn't do it.
i'm using palemoon atm, which reflects firefox 26 iirc, so my "why" was direct more towards the first part of your explanation (iceweasel >=48).
i don't think i will actually ever need the repository index on a web page, and far be it from me to criticize.

on inox (chromium fork) and qupzilla i get this in a green box:
"It looks like you are using Chromium or Chrome. This page will only work on version >=48 with experimental JavaScript features (‘harmony’) enabled."

on dillo (yay!) i get this in a red-bordered box:
"The repository index is rendered by your browser using JavaScript, which
is used for retrieving and processing the package lists from our
repository. Without JavaScript, this page stays empty.
Allow scripts originating from the bunsenlabs.org domain to run, or view the directory index instead.
You may also inspect the script before running it."

on palemoon i get a blank page (except for the top menu bar).

Last edited by ohnonot (2016-02-11 21:17:51)

johnraff · 2016-02-12 05:14:35

I'm currently getting a blank page (except for the navigation top bar) on Iceweasel 43.0.4
It worked OK before.

#1 2016-02-10 23:07:37

Backports Repository Index - add relevant discussion thread

#2 2016-02-11 01:57:30

Re: Backports Repository Index - add relevant discussion thread

#3 2016-02-11 02:42:02

Re: Backports Repository Index - add relevant discussion thread

#4 2016-02-11 02:51:40

Re: Backports Repository Index - add relevant discussion thread

#5 2016-02-11 03:12:57

Re: Backports Repository Index - add relevant discussion thread

#6 2016-02-11 03:18:06

Re: Backports Repository Index - add relevant discussion thread

#7 2016-02-11 06:07:18

Re: Backports Repository Index - add relevant discussion thread

#8 2016-02-11 06:30:38

Re: Backports Repository Index - add relevant discussion thread

#9 2016-02-11 07:27:47

Re: Backports Repository Index - add relevant discussion thread

#10 2016-02-11 07:44:56

Re: Backports Repository Index - add relevant discussion thread

#11 2016-02-11 21:17:19

Re: Backports Repository Index - add relevant discussion thread

#12 2016-02-12 05:14:35

Re: Backports Repository Index - add relevant discussion thread

Board footer