ungoogled-software / contrib Goto Github PK

I have put together a set of scripts that make it possible to convert the Debian source packaging of Chromium into an equivalent ungoogled-chromium package. The end result is not only very close to what a native packaging of u-c would look like (all that's missing is u-c-specific documentation), it can be installed on the system concurrently with the original Chromium (because all the files that would otherwise conflict have been renamed).

Note that the converted package retains the original upstream source tarball used by Debian. Yet it does not require the ungoogled-chromium tooling to build, because the necessary modification logic is condensed into a script generated by the new make_domsub_script.py utility. This generated script is invoked as an additional patching operation during the package build, and its effects can also be reverted, all in accordance with Debian package policy.

By design, the delta between the Debian package and the converted one is as small and easily-reviewable as possible. I've even provided a script (compare.sh) to facilitate this. (This is why I opted against bundling the domain substitutions as a patch. No additional scripts would have been needed, but the patch was over 30 MB in size!)

The new work may be viewed in my tree here. Please have a look at it, perhaps give it a try, and let me know if you have any feedback.

Before I put together a proper PR, I would like to ask if it should land here in the contrib repo, or if this approach might be desirable for ungoogled-chromium-debian instead. I believe that the approach implemented here could be generalized to other Linux distros, allowing u-c releases to piggyback directly on the release-engineering work that the distros already perform.

We cannot simply bunch everything in the top-level folder, right? Therefore I propose the following structure to establish it from the beginning.

Starting from the top

• README.md — Has the already-written introduction and the list of all topic-folders with active links with a brief description of what one finds there
• Topic_folder — We need to sort and categorise contributions based on their nature, I think. I suggest, for example:
• Fixes — Some fixes, which are targeted at specific use-cases, not applicable generally in other repos
  • README.md — Each level has its own README.md with a list of all the contributions at that level
  • a_single_file — If a contribution consists of a single file, it stays on its own and has a detailed enough description in a corresponding README.md at this level (the one mentioned above)
  • a_folder_with_descriptive_name — Is used if a contribution needs more, than a single file
    • README.md — A detailed description of this contribution, usage examples, etc. License maybe.
    • file1
    • file2
    • subfolder_if_needed
• Features — Some ideas and implementations
  • Same structure here
• Scripts — Various scripts
  • Same structure here
• What else do we need?
  • Suggestions — welcome!

When we finally come to the agreement, if nobody minds of-course, I will take the liberty to create a pull request with the agreed-upon structure.

when bookmarks is exported the file must be generated in the downloads folder, if uninstalled it is lost because it is saved in the installation folder
thks

I'm pretty unsure whether this repo is the right place to post at...

I am curious about the idea of ungoogled Chromium OS.

Recently, the Chromium Project announced to widely support Chromium OS as a regular Linux distro users may run on any x86 machine. Unfortunately, the aim of this project is not to provide an ungoogled Chromium OS, but more likely to push the Google related projects on many x86 systems too.

In regard of this step, I was wondering whether it would be possible to provide generic ungoogled Chromium OS builds too.

Why should anyone use ungoogled Chromium OS?

At the moment, Chromium OS is one of the few Linux distros / desktop environments properly supporting touch screens, Stylus input and convertible devices.
Moreover, Chromium OS is pretty well eligible for Android development as it natively runs Android applications.

Unfortunately, aside of Google's Chrome OS, there are currently only two other notable Chromium OS distros; Fyde OS and CloudReady. Both are addicted to cloud services and shipped with proprietary software.

What's simply missing, is a libre, ungoogled Chromiums OS build somewhere.

Hi, I would like to improve ungoogled-chromium repo / the repos of the org.

As a first small step I would like to create a .github repository
to give the organization a better overview of the repositories.