Opkg feeds

Requires: !178 (merged)

changed milestone to %8

assigned to @mvaner

Is it allowed to have spaces before the src/gz? I don't know the format, but I'd guess that might be legal.

Also, if we didn't care about properly reporting malformed lines, we could do the whole thing on a single match. But that's not important.

I didn't found out any information if it's possible. Debian's relevant file specifies nothing about space before it. I would say that it doesn't seems to be a problem and if it will be, then let's solve it when it is.

I just tested it and opkg accepts the definitions with leading whitespace. I'd vote for fixing it now, because these will warrant hard-to-track-down bug reports. Especially when the only needed change is to use '^%s*src/gz ' instead of the current regexp, which is even less work than writing your proposition to leave it for later :-P.

Well reality is that I didn't wanted to think about consequences. O:-)

Everybody is seems to be adding it without white character in front. But in depth, there should be no harm if there is one. So it's there.

Apart from the whitespace at the line start I think the code looks OK. But this is something to test in real life, mostly.

assigned to @kkoci

This code is written for some time. But if I remember that I was testing it. But yes, real test is required. Let's test it in test branch.

assigned to @mvaner

assigned to @kkoci

added 1 commit

• ff6dd6a8 - fixup! fixup! Source opkg custom feeds

Compare with previous version

assigned to @mvaner

Thanks, let's put it in.

assigned to @kkoci

added 1 commit

• c6268e72 - Source opkg custom feeds

Compare with previous version

merged

added Feature label and removed 1 deleted label

unmarked as a Work In Progress

changed milestone to %Turris OS 3.7