Does anyone still support a distro that uses libudev.so.0?

[Lei Zhang]

Hi Chromium packagers,

I did a bunch of work years ago in https://crrev.com/305314 and
https://crrev.com/305348 so Chromium can run on Linux distros with
either libudev.so.0 or libudev.so.1. It's been a while, so I would
like to undo my work. At the very minimum, I would like to remove the
checks for libudev.so.0. I would also like to remove the dynamic
loading mechanism to further simplify things.

Before taking any actions, I'm wondering if anyone is still running
modern Chromium on a Linux distro that uses libudev.so.0. I think RHEL
6 ships with libudev.so.0, but support for RHEL 6 looks to be at the
end, assuming I read RedHat's lifecycle info correctly.

[Olivier Tilloy]

On Thu, Sep 17, 2020 at 9:53 AM Lei Zhang <the...@chromium.org> wrote:
>
> Hi Chromium packagers,

Hi Lei,

> I did a bunch of work years ago in https://crrev.com/305314 and
> https://crrev.com/305348 so Chromium can run on Linux distros with
> either libudev.so.0 or libudev.so.1. It's been a while, so I would
> like to undo my work. At the very minimum, I would like to remove the
> checks for libudev.so.0. I would also like to remove the dynamic
> loading mechanism to further simplify things.
>
> Before taking any actions, I'm wondering if anyone is still running
> modern Chromium on a Linux distro that uses libudev.so.0.

Not Ubuntu. The oldest supported release is 16.04 (xenial), and it has
libudev.so.1.

[Tomáš Popela]

Hi Lei,

Dne čtvrtek 17. září 2020 v 9:53:26 UTC+2 uživatel Lei Zhang napsal:

Hi Chromium packagers,

Before taking any actions, I'm wondering if anyone is still running
modern Chromium on a Linux distro that uses libudev.so.0. I think RHEL
6 ships with libudev.so.0,

Yes, that's true.

 

but support for RHEL 6 looks to be at the
end, assuming I read RedHat's lifecycle info correctly.

And that's true as well. It will go EOL by the end of November 2020. But we will rebase to the newer version until that happens. So if you could target a Chromium major version that won't be in stable channel at that point, we would appreciate it. According to https://www.chromestatus.com/features/schedule it probably will be Chromium 88.

Bye,

Tom (Red Hat)

[Dirk Pranke]

Chrome itself still supports Trusty (14.04), so we'd still need to be careful if it only has .0.

-- Dirk

 

--
You received this message because you are subscribed to the Google Groups "chromium-packagers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-packag...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-packagers/CAKyXnk9TMfKs3diyM12U72Mm10RSpbHLbyL1WWZ0LZGtRw9P%2Bg%40mail.gmail.com.

[Olivier Tilloy]

On Thu, Sep 17, 2020 at 6:19 PM Dirk Pranke <dpr...@google.com> wrote:
>
>
>
> On Thu, Sep 17, 2020 at 1:00 AM Olivier Tilloy <olivier...@canonical.com> wrote:
>>
>> On Thu, Sep 17, 2020 at 9:53 AM Lei Zhang <the...@chromium.org> wrote:
>> >
>> > Hi Chromium packagers,
>>
>> Hi Lei,
>>
>>
>> > I did a bunch of work years ago in https://crrev.com/305314 and
>> > https://crrev.com/305348 so Chromium can run on Linux distros with
>> > either libudev.so.0 or libudev.so.1. It's been a while, so I would
>> > like to undo my work. At the very minimum, I would like to remove the
>> > checks for libudev.so.0. I would also like to remove the dynamic
>> > loading mechanism to further simplify things.
>> >
>> > Before taking any actions, I'm wondering if anyone is still running
>> > modern Chromium on a Linux distro that uses libudev.so.0.
>>
>> Not Ubuntu. The oldest supported release is 16.04 (xenial), and it has
>> libudev.so.1.
>
>
> Chrome itself still supports Trusty (14.04), so we'd still need to be careful if it only has .0.

Trusty also has libudev.so.1 (systemd 204), so that should be fine.

[Lei Zhang]

Thanks for the feedback so far. I'll wait and see if anyone else
chimes in for other distros.

On Thu, Sep 17, 2020 at 1:30 AM Tomáš Popela <tomas....@gmail.com> wrote:
> And that's true as well. It will go EOL by the end of November 2020. But we will rebase to the newer version until that happens. So if you could target a Chromium major version that won't be in stable channel at that point, we would appreciate it. According to https://www.chromestatus.com/features/schedule it probably will be Chromium 88.

I have no plans to work on this immediately, so this will definitely
be for Chromium 88 or later. Just wanted to get the conversation
started.

[Mike Frysinger]

couldn't we use UMA for this sort of thing ?

-mike

--
You received this message because you are subscribed to the Google Groups "chromium-packagers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-packag...@chromium.org.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-packagers/CACSHbcRDVhA25ecO1LdsFSmPn9KjqZQ%3DJ_Kaz-Gw5KQCyvRA8g%40mail.gmail.com.

[Eric Hameleers]

Hi Lei

The Slackware platforms for which I provide Chromium packages (latest stable aka Slackware 14.2, and also the development release aka slackware-current) all ship libudev.so.1.

Cheers, Eric

Op donderdag 17 september 2020 om 09:53:26 UTC+2 schreef Lei Zhang:

[Lei Zhang]

On another issue, we found base::debug::DumpWithoutCrashing() gave us
the feedback we needed without the overhead of adding an UMA. I've
filed https://crbug.com/1237497 for this work.

> To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-packagers/CAAbOScnGLPcczqF0XecRSSbQC5EmgJ-542YBApdVtYUZmAhgXg%40mail.gmail.com.