Skip to content
This repository has been archived by the owner on Apr 20, 2021. It is now read-only.

Big Changes: new standard #105

Open
Wabri opened this issue Feb 8, 2019 · 0 comments
Open

Big Changes: new standard #105

Wabri opened this issue Feb 8, 2019 · 0 comments
Labels
configurations Edit configuration files enhancement New feature or request scripts New package or edit script

Comments

@Wabri
Copy link
Owner

Wabri commented Feb 8, 2019

I thought about trying to use configparser for define the installer of the package, by deleting the .sh file and turning it into a configuration file. For example:

[DEFAULT]
name = # this is the string of how the package can be called (maybe a list of name can also be useful)
description = # same as description that are now in use
url = # same as url that are now in use
class = # this is referred to issue #52 en give the type of the package

[Common]
dekstop_entry = # this is empty if the package didnt have the DE otherwise it provides the folder
installed = # this is empty if the package is not installed, otherwise it provides the folder where it was installed
cache = # give the directory of the download resource

[Script]
download = # command to download resource of the script
before_install = # script before install
install = # script installer
after_install = # script after install
unistall = # script to uninstall the package (if installed)
desktop_entry = # definition of desktop_entry (if required)

With this new method we can do a lot of different things, but obviously we need to change a lot of code.
Also this method are maybe more readable for some users, but we can understand that only before implementation.

I need some feedback to improve this idea.

@Wabri Wabri added enhancement New feature or request scripts New package or edit script configurations Edit configuration files labels Feb 8, 2019
@Wabri Wabri added this to the YAPI Origin 1.0.0 milestone Feb 8, 2019
Wabri added a commit that referenced this issue Mar 30, 2019
Wabri added a commit that referenced this issue Mar 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
configurations Edit configuration files enhancement New feature or request scripts New package or edit script
Projects
None yet
Development

No branches or pull requests

1 participant