nerd/rufus
1
1
Fork 0
mirror of https://github.com/pbatard/rufus.git synced 2024-08-14 23:57:05 +00:00
Code Issues 1 Projects Releases Wiki Activity
rufus/res/appstore/Package.appxmanifest

59 lines
2.1 KiB
Text
Raw Normal View History

[internal] add Windows AppStore project files * These are the settings used to publish the official app at: https://www.microsoft.com/store/apps/9PC3H3V7Q9CH
2021-02-03 20:14:14 +00:00
<?xml version="1.0" encoding="utf-8"?>
<Package
xmlns="http://schemas.microsoft.com/appx/manifest/foundation/windows10"
xmlns:uap="http://schemas.microsoft.com/appx/manifest/uap/windows10"
[misc] fix a warning in msapi_utf8.h Also set the AppStore default codepage to UTF-8
2021-03-25 19:27:27 +00:00
xmlns:uap7="http://schemas.microsoft.com/appx/manifest/uap/windows10/7"
xmlns:uap8="http://schemas.microsoft.com/appx/manifest/uap/windows10/8"
[internal] add Windows AppStore project files * These are the settings used to publish the official app at: https://www.microsoft.com/store/apps/9PC3H3V7Q9CH
2021-02-03 20:14:14 +00:00
xmlns:rescap="http://schemas.microsoft.com/appx/manifest/foundation/windows10/restrictedcapabilities"
[misc] fix a warning in msapi_utf8.h Also set the AppStore default codepage to UTF-8
2021-03-25 19:27:27 +00:00
IgnorableNamespaces="uap uap7 uap8 rescap">
[internal] add Windows AppStore project files * These are the settings used to publish the official app at: https://www.microsoft.com/store/apps/9PC3H3V7Q9CH
2021-02-03 20:14:14 +00:00
<Identity
Name="19453.net.Rufus"
Publisher="CN=7AC86D13-3E5A-491A-ADD5-80095C212740"
[grub] add yet another frigging patch to GRUB "2.04" * GRUB 2.0 maintainer think they're doing a fine job, even when there are CRITICAL SECURITY FIXES that should warrant an immediate out of bound release, and instead consider that waiting MONTHS or YEARS to release anything is not a big deal at all. * Ergo, distros, such as Ubuntu, start to pick whatever security patches they see fit, since they can simply not RELY on the upstream project to produce security releases in a timely manner. One such patch is: https://lists.gnu.org/archive/html/grub-devel/2021-03/msg00012.html * But since there is no new GRUB release per se, they still call their GRUB version, onto which they applied patches that have come into existence more than 2 years after the actual 2.04 release, "GRUB 2.04". * Obviously, since GRUB 2.04 + literally hundreds of cherry picked patches does deviate a lot from the last release, THINGS BREAK IN SPECTACULAR FASHION, such as the recently released Ubuntu 21.04 failing to boot with the error: grub_register_command_lockdown not found. * Oh, and of course, regardless of all the above, if you ask anyone, they'll tell you that there's nothing fundamentally wrong with the GRUB release process (even if they should long have released 2.05, 2.05-1 and 2.05-2, were their maintainer ready to acknowledge that delaying releases DOES CREATES MAJOR ISSUES DOWSTREAM, as many people REPEATEDLY pointed to them on the GRUB mailing list) or with the Ubuntu GRUB versioning process (that really shouldn't be calling their version of GRUB "grub-2.04" but instead something like "grub-2.04_ubuntu"). Oh no siree! Instead, the problem must all be with Rufus and its maintainer, who should either spend their lives pre-emptively figuring which breaking patch every other distro applied out there, or limit media creation to DD mode, like any "sensible" person would do, since DD mode is the ultimate panacea (Narrator: "It wasn't"). * So, once again, a massive thanks to all the people who have been involved in the current GRUB 2.0 shit show, whose DIRECT result is to make end users' lives miserable, while GRUB maintainers are hell bent on continuing to pretend that everything's just peachy and are busy patting themselves on the back on account that "Fedora recently dropped more than 100 of the custom patches they had to apply to their GRUB fork" (sic). Nothing to see here, it's just GRUB maintainer's Jedi business as usual. Besides, who the hell cares about Windows users trying to transition to Linux in a friendly manner anyway. I mean, as long as something doesn't affect existing Linux users, it isn't a REAL problem, right?...
2021-04-22 22:59:17 +00:00
Version="3.14.1778.0" />
[internal] add Windows AppStore project files * These are the settings used to publish the official app at: https://www.microsoft.com/store/apps/9PC3H3V7Q9CH
2021-02-03 20:14:14 +00:00
<Properties>
<DisplayName>Rufus</DisplayName>
<PublisherDisplayName>Akeo Consulting</PublisherDisplayName>
<Logo>Images\StoreLogo.png</Logo>
</Properties>
<Dependencies>
<TargetDeviceFamily Name="Windows.Desktop" MinVersion="10.0.14393.0" MaxVersionTested="10.0.19042.572" />
</Dependencies>
<Resources>
<Resource Language="x-generate"/>
</Resources>
<Applications>
<Application Id="Rufus"
Executable="rufus\rufus.exe"
[appstore] don't exit on unhandled parameters * Looks like executables installed from the Windows Store launch with a "/InvokerPRAID" added parameter, which of course BREAKS apps that have a defined set of parameters and don't except that Microsoft would gingerly add random unwanted stuff there... * The provision of this extra parameter also appears to be tied to using one of: - <TargetDeviceFamily Name="Windows.Universal" ...> - <uap:SplashScreen ...> - <Application EntryPoint="$targetentrypoint$" ...> in the appxmanifest. * This resulted in our argument processing loop to cause early exit on account that an unexpected option was provided. * Fix this by adding an explicit check for /InvokerPRAID and not exiting on unhandled params and removing or altering the 3 appxmanifest options listed above. * Also set an explicit Windows.FullTrustApplication and remove splash screen. * Also update _pre-commit.sh to update appstore build number automatically. * Also remove splash screen images, add store listing CSV and toggle App builds to manual. * Closes #1690
2021-02-05 17:20:54 +00:00
EntryPoint="Windows.FullTrustApplication">
[internal] add Windows AppStore project files * These are the settings used to publish the official app at: https://www.microsoft.com/store/apps/9PC3H3V7Q9CH
2021-02-03 20:14:14 +00:00
<uap:VisualElements
DisplayName="Rufus"
Description="Rufus"
BackgroundColor="transparent"
Square150x150Logo="Images\Square150x150Logo.png"
Square44x44Logo="Images\Square44x44Logo.png">
[net] switch to INetworkListManager::GetConnectivity to detect connectivity * InternetGetConnectedState() is next to useless and doesn't provide coherent outcome on the ARM64 platform I'm testing with. This results in Rufus declaring that Internet is unavailable on platforms that do have actual Internet connectivity. * Swicth to using INetworkListManager::GetConnectivity(), which actually reports a dependable result. * Closes #1691 * Also remove the mutex for uprintf(), which may produce thread lockout and remove an unwanted double GetSignatureName() call on startup.
2021-02-06 18:58:42 +00:00
<uap:DefaultTile Wide310x150Logo="Images\Wide310x150Logo.png" Square71x71Logo="Images\SmallTile.png" Square310x310Logo="Images\LargeTile.png">
<uap:ShowNameOnTiles>
<uap:ShowOn Tile="square150x150Logo"/>
<uap:ShowOn Tile="wide310x150Logo"/>
<uap:ShowOn Tile="square310x310Logo"/>
</uap:ShowNameOnTiles>
</uap:DefaultTile >
[internal] add Windows AppStore project files * These are the settings used to publish the official app at: https://www.microsoft.com/store/apps/9PC3H3V7Q9CH
2021-02-03 20:14:14 +00:00
</uap:VisualElements>
[misc] fix a warning in msapi_utf8.h Also set the AppStore default codepage to UTF-8
2021-03-25 19:27:27 +00:00
<uap7:Properties>
<uap8:ActiveCodePage>UTF-8</uap8:ActiveCodePage>
</uap7:Properties>
[internal] add Windows AppStore project files * These are the settings used to publish the official app at: https://www.microsoft.com/store/apps/9PC3H3V7Q9CH
2021-02-03 20:14:14 +00:00
</Application>
</Applications>
<Capabilities>
<rescap:Capability Name="runFullTrust" />
<rescap:Capability Name="allowElevation" />
</Capabilities>
</Package>
Reference in a new issue Copy permalink