The community testing repository: purpose, maintainers and installation boundaries

"Linyaps Community Test Source" is created by community enthusiasts @mozixun、 @罐子 The third-party community sharing project jointly created is essentially a supplementary repository for Linyaps applications.

As a project purely contributed by community enthusiasts, it is built entirely on the spontaneous strength of the community. Its core positioning is "complementation and expansion of official sources"—— does not replace the official source, but focuses on subdivided scenes that are not yet covered by the official source. Through flexible adaptation and rapid iteration, it provides users with richer Linyaps application usage options, making the Linyaps ecosystem more suitable for diverse needs.

For all Linyaps users, the core value of this community project lies in accurately solving actual pain points and significantly improving the user experience - it can not only break the boundaries of distributions, but also allow non-deepin users to Users can use Linyaps applications more smoothly; they can keep up with demand and quickly adapt to new functions and new hardware without waiting for long official iterations; they can also make applications more lightweight and flexible through technical optimization, and because Linyaps applications are naturally isolated from key components of the host system, as long as the application is not repeatedly installed during mixed-source use, it will not have an impact on the system, completely eliminating the risk of system failure that may be caused by mixed-source traditional distributions; it can also activate the vitality of co-construction, allowing user needs to directly promote ecological improvement.

1. Who is suitable to use community testing sources

If you belong to the following types of users, Linyaps community test source will greatly improve your experience:

• Fans of “chasing new things”: I don’t want to wait for the official iteration, I want to experience the new version and new functions as soon as possible.
• New hardware users: When using next-generation core graphics such as AMD Radeon 780M, Intel Iris Xe, or N-card independent graphics, the problem of insufficient official driver adaptation is encountered.
• Co-construction participants: Willing to put forward adaptation requirements and participate in test feedback to help improve the Linyaps ecosystem.

2. We solved these problems

The project initiator has delivered visible results through a series of technical challenges and precise adaptation, which not only ensures technical professionalism, but also directly benefits users, especially forming core breakthroughs in "pursuing innovation".

Unify the latest Base environment

• In view of the pain point that the old official version of Base cannot drive new graphics cards, and that domestic closed-source driver graphics cards, N cards, etc. cannot work properly, all applications included in the library are built based on the latest version of org.deepin.base (such as 25.2.1), and commercial applications are given priority to adapt to the latest professional version of Base.
• Once there is a Base update that cannot be smoothly migrated, it will be upgraded simultaneously as soon as possible to avoid the root cause of the compatibility issues between the old version of Base and non-deepin distribution new systems and new kernels, allowing applications such as QQ and DingTalk to run stably in multiple systems.

Complete driver shortcomings and cover different hardware requirements

• Focusing on the pain points of non-deepin distribution N card users, the official source currently only provides deepin exclusive early N card drivers, while the community source continues to follow up the user mode driver iteration. The production of the 580.95.05 driver has been completed, and the 580.105.08 version driver is being produced to ensure that the user mode of the driver accurately corresponds to the kernel mode.

• Ensure the normal operation of new-generation core displays such as AMD Radeon 780M and Intel Iris Xe, as well as domestic closed-source driver graphics cards and N-cards, covering mainstream and niche hardware, so that new hardware users of different releases can use the Linyaps application normally.
• N card closed-source user mode driver adaptation will continue until the NOVA+NVK combination enters the main line of Linux distributions to achieve long-term compatibility.

Unify Runtime independently to reduce the size occupied by the application itself

• It took two days and two nights to overcome the WebKit2gtk link problem and develop it independently. org.deepin.runtime.gtk4 (version 25.2.1.0) , and completed the adaptation to the latest Base, and has been officially built into the community source.

• solves the unnecessary memory expansion problem caused by some Flutter applications/Tauri applications requiring their own webkit2gtk. Currently, Flutter, Tauri and other applications that rely on WebKit2gtk can directly call the unified runtime, greatly improving the adaptation efficiency.

3. What actual gains can you get?

Improved cross-release consistency experience

Non-deepin users such as Ubuntu, Fedora, ArchLinux, and CachyOS can now run Linyaps applications such as QQ, DingTalk, Venera, and Biliup-app smoothly, completely getting rid of the "system incompatibility" problem.

Application size is greatly optimized

Thanks to unified runtime support, applications do not need to build in redundant dependency libraries. The package size of Biliup-app (v1.0.2) is only 8.6 MiB, and Venera (v1.6.0) is only 16.9 MiB. Download and installation are faster and occupy less storage.

Rapid iteration of version updates

For example, Venera and Biliup-app have been upgraded to the latest versions to implement native build support. There is no need to wait long to apply new functions and bug fixes.

4. How to use community testing sources

Add community feed

Add application source (obtain adapted applications)

sudo ll-cli repo add --alias=testing stable https://cdn-linglong.odata.cc

Add build source (for developer use)

ll-builder repo add --alias=testing stable https://cdn-linglong.odata.cc

Tips for using mixed sources (taking into account stability and new functions)

If you want to use official sources (to ensure daily stability) and community sources (to experience new adaptations) at the same time, you can reset the priority through the following command. The two do not conflict with each other:

sudo ll-cli repo set-priority testing 0 && sudo ll-cli repo set-priority stable 0

Note: Because Linyaps is isolated from key components of the host environment system, the use of mixed sources will not affect the stability of the host system. The initial state can be restored after uninstalling the application without any residue.

5. Participate in community co-construction

If you have application needs that you want to adapt, or encounter usage problems, you can join the exclusive QQ group (979437558) to communicate directly with the project initiator and other users - your feedback will directly promote the iteration of the project and make the Linyaps ecosystem more in line with everyone's needs.

"Linyaps Community Test Source" is a project completely created by community enthusiasts. There is no complicated concept packaging, only Solid technology, practical solutions, and flexible experience . Especially for users of non-deepin distributions, it truly breaks the system boundaries and allows Linyaps applications to reach more scenarios. It also provides more flexible and efficient usage options for users with new hardware and who love to pursue new things.

If you are troubled by related pain points, you might as well try this community source; friends who are willing to participate in the test are also welcome to join and make the Linyaps application more useful together!