Currently only desktop environments are supported, through this
feature.
I still can't limit the menu, since the ${ARCH} information
from the board is sourced from the board configuration file,
just after displaying all the menus.
So ATM, an error will be displayed if you select a desktop
environment :
* with a "only_for" file present in its directory
* without the architecture name (arm32, arm64) being written
inside the "only_for" file.
The next step is to generalize that for appgroups.
Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr>
Can I say how bad merge tools are in 2020 ?
Meld is REALLY confusing to use.
So new issues may have arise due to bad merging (only).
Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr>
Turns out that packages at the beginning, or at the end of
the packages list were not filtered correctly.
Also the Desktop packages list needed to be filtered too.
Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr>
packages.remove can now be placed inside cli/main,
desktop/environments and desktop/appgroups directories
in order to remove packages from the list of packages
to install.
Note that this does NOT trigger an apt remove. This
just remove the package from the list of packages to
install.
That said, if you install a package that clearly depends
of the "removed" package, it will be installed anyway.
Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr>
The base logic of the CLI support is now tested.
However the package.remove feature is still untested ATM.
The APT install options menu has been removed, but the variable
is still there. You can still set it to "suggests recommends" if
you want to generate a nice 10GB image.
I'm barely kidding here, APT goes CRAZY if you enable
--install-suggests and --install-recommends for anything.
So the option is now available for experimented builders only.
Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr>
- add transmission-remote
- change libre office style
- add support for gdm3
- add new packages group for gnome3 - languages and install a few most used packs by default
* rm board uboot
* merging to head
* add new xorg config
* adding new asound files
pine-book-pro and rk3399
* fixing image-helper
* chaanged to apt-get from apt
* working to fix image-helpers.sh
* Readd heli
* Remove spaces
Co-authored-by: richneese <r.neese@gmail.com>
The whole point is to get away, as much as possible, from the
Bash script, and use only easy to read configuration files.
For that purpose, the Desktop packages system is being mimicked
for the standard command-line only images.
New folders have been added :
* config/cli/${RELEASE}/debootstrap
* config/cli/${RELEASE}/main
Both parts can contain :
* packages
* config_${SELECTED_CONFIGURATION}/packages
* custom/boards/${BOARD}/packages
* custom/boards/${BOARD}/config_${SELECTED_CONFIGURATION}/packages
For the "main" part, you can also have packages.additional in the
same folder. These files will use to populate the PACKAGES_LIST_ADDITIONAL
variable.
For the "debootstrap" part, you can also have "components" files,
which will be used to populate the DEBOOTSTRAP_COMPONENTS variable.
This is still untested for the moment, so don't use it unless you
can fix it.
Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr>
* Change Ubuntu Eoan to Ubuntu Groovy and enable it as CSC
Tested CLI and desktop image, but needs cache creation and repository before it will be possible to build without error.
* Update Groovy compiler for chroot
* Adjust pkg dependencies for groovy
Sadly htop doesn't build
* Don't delete /boot/armbianEnv.txt file at least for meson64
fix for #2249 ODroid-N2 armbian-config-->hardware menu not work
* Update meson.txt
* Update boot-odroid-n2.ini
Co-authored-by: Igor Pečovnik <igorpecovnik@users.noreply.github.com>
Even though, its use should be limited as much as possible.
Third party APT repositories are the biggest source of problem and
instabilities, when commonly used packages start to being pulled from
them.
Still, some required packages (like graphics drivers, patched
media players, ...) require third party APT repositories, so the
possibility to source from third party APT repositories has been
added.
You can also provide the GPG keys, if the repository isn't a PPA
and add-apt-repository cannot get the key automatically.
Again, adding GPG key is extremely dangerous. If you accept GPG
keys from malicious individuals, your system will provide you with
no warnings when you install malicious packages signed with these keys.
Still, there are repositories, like the Docker one, which require
adding the GPG key by hand.
Note that the current system doesn't provide anyway to source the
GPG from a keyserver yet.
I didn't add this feature since I don't know many third-party APT
repositories (at all), which won't provide GPG keys automatically
(like Launchpad PPA) but have keys that can be still be sourced from
a GPG server...
Still, the feature is implemented, it works... but should only be
mainly used by people customizing the images for their needs.
On the Armbian side, we are going to put all the Debian packages,
required for the traditional Armbian installation, on Armbian
repositories.
Also :
* In order to provide the ability to add APT repositories,
add-apt-repository is required. For that purpose, the list
of packages required by the Desktop options is now kept separate.
During debootstrap :
* the 'standard' package are installed first, in order to get
add-apt-repository;
* then the APT repositories are added;
* then the Desktop packages are installed;
There's still a bug remaining on that regard. APT repositories
and Desktop phases should be skipped if "BUILD_DESKTOP != yes".
This will be fixed in the next commits.
* In order to preserve the list of Desktop packages, a new variable
"DEBIAN_RECOMMENDS" has been added to
desktop.sh: create_desktop_package() . This variable is now used
for storing comma-separated list of recommended packages.
* I reverted part of the clutter added to the builder Docker
configuration.
* I replaced vague checks ( != "no" ) by precise checks ( == "yes" )
for Desktop options, so that options like KERNEL_ONLY don't
trigger Desktop related questions. This still needs to be
thoroughly tested, but this should resolve#12 .
Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr>
The best way to add PPA and APT repositories on Ubuntu systems, at
least, is to use add-apt-repository .
However add-apt-repository requires software-properties-common .
On Armbian, this package is installed along the other packages, but
if we want to add PPA repositories BEFORE triggering the packages
installation, we need this package installed before.
Now, installing software-properties-common during Deboostrap causes
the process to stop.
So... Two solutions :
1. Split the installation of the "PACKAGE_LIST" in order to install
the main package list (the one that will be installed no matter what),
and the Desktop packages list which is only required to install
the selected Desktop items.
This is the approach being tested right now. I still have to check
if that works well.
2. Forget about add-apt-repository and force the addition of 3rd party
repositories through files, similar to /etc/apt/sources.list.d . This
approach makes adding PPA a bit more difficult, since you have to
2.1 Find the real APT URL
2.2 Find the GPG key used to sign the packages
I'll take the second approach if the first one causes some issues.
Still, I didn't think that "just" adding APT repositories would be
so cumbersome.
Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr>
So that people clearly identify them as "apps", and not
just some random libraries... Though we still provide
GCC and Clang through this system...
We'll see if we go back to the old naming system on that
one.
Signed-off-by: Miouyouyou (Myy) <myy@miouyouyou.fr>
