Package Details: microsoft-edge-dev-bin 125.0.2535.6-1

Git Clone URL: https://aur.archlinux.org/microsoft-edge-dev-bin.git (read-only, click to copy)
Package Base: microsoft-edge-dev-bin
Description: A browser that combines a minimal design with sophisticated technology to make the web faster, safer, and easier
Upstream URL: https://www.microsoftedgeinsider.com/en-us/download
Licenses: custom
Conflicts: microsoft-edge
Provides: microsoft-edge
Submitter: ejiek
Maintainer: bittin (josc, ejiek, SolarAquarion)
Last Packager: bittin
Votes: 98
Popularity: 0.58
First Submitted: 2020-10-20 22:29 (UTC)
Last Updated: 2024-04-29 11:29 (UTC)

Dependencies (16)

Required by (3)

Sources (3)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 15 Next › Last »

bittin commented on 2023-02-26 15:20 (UTC)

@xatierlike: yeah updated the package today (sorry it took some days)

xatierlike commented on 2023-02-25 23:56 (UTC)

microsoft-edge-dev_112.0.1698.0-1_amd64.deb is out at 22-Feb-2023 23:05

bittin commented on 2023-02-11 12:00 (UTC)

@ioan: The new version is only out for Windows 11 so far, will package it up when Microsoft uploads a Debian package

ioan commented on 2023-02-11 11:58 (UTC)

Notice for the chatGPT/copilot u need the version 111.0.1660.9

jvybihal commented on 2022-12-14 13:32 (UTC)

This package has 5 maintainers, and it is still in constant out-of-date state. Wtf guys?

https://packages.microsoft.com/repos/edge/pool/main/m/microsoft-edge-dev/microsoft-edge-dev_110.0.1556.0-1_amd64.deb

bittin commented on 2022-09-15 04:17 (UTC)

@stevensko: thanks for the headsup downgraded the package now again

stevensko commented on 2022-09-14 20:59 (UTC)

seems that microsoft removed the 107.0.1379.1-1 .deb build from being available for download in favor of 107.0.1375 again

xatierlike commented on 2022-04-18 00:16 (UTC)

Note that # in microsoft-edge-{stable,dev,beta}-flags.conf are not supported by the launcher script, I tried to update the chromium wiki page but got reverted. ¯_(ツ)_/¯

https://wiki.archlinux.org/index.php?title=Chromium&diff=next&oldid=726807

alerque commented on 2022-03-07 06:32 (UTC)

@hzmi No all those conflicts/provides are bogus. They shouldn't be on the other packages either. Only the one canonical package name (usually the source build) should be included in conflicts/provides, and other packages that conflict/provide with that package will automatically do so with each-other. Everybody else stuffing this field with extra values is doing it wrong.

hzmi commented on 2022-02-25 12:29 (UTC)

Shouldn't conflicts and provides be the same like the sister packages like microsoft-edge-stable-bin and microsoft-edge-beta-bin?

The conflicts should be edge, edge-dev, edge-dev-bin, microsoft-edge-dev and provides should be edge-dev, microsoft-edge-dev.

Or is there something that makes this package an exception?