985 replies to this topic

[WanWizard]

Is not going to happen any time soon.

 

I've looked at it, 1.1 has a completely rewritten API, so most stuff out there, including OpenSSH, will no longer compile. Not an option.

[rantanplan]

I can not quite understand that ...

pli has 2 'rc' branches. These serve as a kind of 'security' a solid image.
develop is currently maintained only half of pyro. Why is not this at least adapted to the state of the current pyro?

Sumo is already an old branch from the OE core.
Does not seem to go in the right direction either.
I would find it nice if the develop the latest version of pyro.

Then a few quite long since mentioned adjustments -> see, for example Mention of gst @christopher

but are just my ideas :-)

greetings

[WanWizard]

We don't have two 'rc' branches. We have only one, which is a branch of develop created last week, in preparation of OpenPLi 7.

 

'sumo' is a feature branch that is still very much work in progress, it's first focus is "everything must compile". Once 7 is released, the rc branch will disappear, sumo will be merged into develop, and then we move on.

[rantanplan]

ok

 

https://openpli.org/.../xtrend/ET10000

 

 

You're right, there are actually 4 Branches, but it's probably intentionally misunderstood.
Is ok too.
Anyway, it was just an idea of ​​mine.

All good.
many Greetings

[WanWizard]

What do you mean my that link? I don't really follow you. I only see current release and previous releases available for download?

 

As to branches:

• release: release image, codebase is frozen, only hotfixes will be applied, current and previous version are built once a week
• rc: test branch for the pending new release, first tested in house, then released for public testing, will become openpli-7.0-rc soon
• develop: next release codebase
• feature: branches to develop things beyond the next release codebase, sumo is such a branch

And the flow is

 

feature branches -> develop -> rc -> release.

 

The images online have no relation to what is actually build, you can see that the last 6.0-release built was in december last year.

[dax]

Just a question: why not a branch from OE master? On master branch are present all the fix/patch in order to build with recent gcc, etc (recent linux distribution)

[betacentauri]

Master is current development status. It's not marked as stable and there might be problems compiling packages. Better use a stable release.

[rantanplan]

@dax

 

'master' is not a good idea, there is constantly updated everything possible and leads to construction errors. You already need a branch with an environment fix.

 

@WanWizard

 

As I said, it's just my little idea.

You say so yourself, hotfixes are maintained in the release branches.
In my view, this is also the case in pyro.
The updates make sense and leave a few other things.
develop is not for nothing the name, right?

Interestingly, some things were taken over from there, but not many things.
Unfortunately, sumo has been mentioned for a very long time.

I'm just saying that I do not understand it, but I also realize that I have no control over it.

But believe then but here on topic over ...
Sorry

greetings

Edited by rantanplan, 7 November 2018 - 17:25.

[Erik Slagter]

Just a week ago I updated sumo with the latest state of OE Sumo. So no "old" stuff there, it's completely up to date. I don't know what you're talking about.

[rantanplan]

Who is talking about sumo?

I'm talking about pyro and the develop branch!
That can not be so difficult to understand, right?

But you always refer to sumo, which will eventually come ....

No matter ...

I am out

[Erik Slagter]

Who is talking about sumo?

Sumo is already an old branch from the OE core.

So apparently you did.
 

I'm talking about pyro and the develop branch!
That can not be so difficult to understand, right?

Your words...
 

No matter ...
I am out

Yeah, good plan, go waste someone else's time with your nonsense and hostility.

[dax]

Just a question: why not a branch from OE master? On master branch are present all the fix/patch in order to build with recent gcc, etc (recent linux distribution)

 

Master is current development status. It's not marked as stable and there might be problems compiling packages. Better use a stable release.

 

@dax

 

'master' is not a good idea, there is constantly updated everything possible and leads to construction errors. You already need a branch with an environment fix.

Thanks. So why not the branch before master? Now it is thud... Is not marked as stable?

Edited by dax, 7 November 2018 - 22:43.

[WanWizard]

I think you grossly underestimate the work involved in an OE upgrade.

[dax]

I think you grossly underestimate the work involved in an OE upgrade.

Becuase i don't understimate the big work my idea is to do it in an up to date branch

[WanWizard]

???

 

The challenge is not the update of OE, the challenge is to make all meta's compatible with that OE again. And to make sure the build environment stays compatible (OpenPLi 4 has different requirements from a Sumo build).

 

We've been working on the Sumo branch for many weeks now, and we're still not at the point where everything compiles...

[Erik Slagter]

@dax So: either start helping us, or stop whining. What is exactly the great thing of having the very latest OE version, that you can't live without and need us to work around the clock to have it working?

Edited by Erik Slagter, 9 November 2018 - 20:52.

[dax]

@dax So: either start helping us, or stop whining. What is exactly the great thing of having the very latest OE version, that you can't live without and need us to work around the clock to have it working?

At first i'm not whining. I pose few simple questions, unpretentious, just to know.
For your information the people like me that use an up to date linux distribution (probably 0,01%) run up against in a lot of problems related to the build process. Of course, for the team is a nonsense work for the 0,01%. And i know also that i can use a different distribution that is supported by oe.

This is the main reason of my questions, but if this disturb you i will never ask again.

Help you will be the goal for the next years because i'm not skilled.
I can live also without oe and other stuff, don't worry.

When/where i ask to somebody of the team to work around the clock?

Edited by dax, 11 November 2018 - 23:07.

[Erik Slagter]

You might want to start in another tone and be more specific. Something "Hello guys, I am dax, I am trying to home build your image and I don't succeed because of <error message from build process>, can you help me?".

 

I guarantee that will give you a lot more help than this accusing tone.

Edited by Erik Slagter, 12 November 2018 - 21:10.

[dax]

Just a question: why not a branch from OE master? On master branch are present all the fix/patch in order to build with recent gcc, etc (recent linux distribution)

 

 

 

Thanks. So why not the branch before master? Now it is thud... Is not marked as stable?

 

 

Becuase i don't understimate the big work my idea is to do it in an up to date branch

 

Could you kindly point me where i had using an accusing tone? For future reference...

But ok, for me matter is closed because i'm also off topic.

[tigrousad]

Hi guys..
I have i'stalled serviceapp, extplsyer and fffmpeg correctly, but when i choose extplsyer as default player, the services still run on "4097", not on "5002" !! Any idea how fix tbis problrm?? Thnk you