diff options
Diffstat (limited to 'python-bronotes.spec')
| -rw-r--r-- | python-bronotes.spec | 285 |
1 files changed, 285 insertions, 0 deletions
diff --git a/python-bronotes.spec b/python-bronotes.spec new file mode 100644 index 0000000..15cd16e --- /dev/null +++ b/python-bronotes.spec @@ -0,0 +1,285 @@ +%global _empty_manifest_terminate_build 0 +Name: python-bronotes +Version: 2.4.1 +Release: 1 +Summary: A commandline note organization tool. +License: MIT License +URL: https://github.com/jwizzle/bronotes +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/34/c6/52b805e6e02818b196e72055f63cdeebd76beccf6af0dac2eda5c09247f4/bronotes-2.4.1.tar.gz +BuildArch: noarch + +Requires: python3-pyyaml +Requires: python3-shtab +Requires: python3-pyperclip +Requires: python3-gitpython +Requires: python3-fuzzy-match +Requires: python3-numpy + +%description +# Bronotes + +Basically a wrapper to access notes in a directory on your system anywhere from the commandline. And keep it in sync with git. + +Functionality so far: + * Create a note directory on your system on first start + * Add new notes + * Remove notes + * Move notes and directories around + * Edit notes with your $EDITOR + * List notes dir in a tree + * Generate autocompletions for zsh + * Execute arbitrary commands in the notes directory + * The show and edit actions search for matching notes if no valid path is given + +## Installation + +```bash +$ pip install bronotes +``` + +On first command a folder to be used is asked. + +### Completions + +For now there's no built-in completions. +ZSH completions can be generated so you can place them where needed: +```bash +$ bnote completions | tee ~/.oh-my-zsh/completions/_BRONOTES +``` + +## Usage + +By default this wraps any shell command you feed it and executes it in your notes directory. When using any of the defined actions (see bnote -h) it will do that instead. +The default can be changed, and the regular shell alternatives for actions like 'rm' can be used by just using the 'exec' action manually. + +```bash +$ bnote -h # For actions overview, actions have their own sub help-pages. +``` + +```bash +$ bnote list +.notes/ +|-- baewfweiogn +|-- testblaat.md +|-- blarpblarp.md +``` + +```bash +$ bnote madness # madness is a great way to browse your markdown files in a local server + start the madness + env production + listen 0.0.0.0:3000 +``` + +* Subcommands have their own help pages. +* When using the edit or show subcommand, it falls back on the -s option if the path to your note is not valid. +* If the first argument given is not recognized by bronotes, a default action will be taken and the first argument will be fed to that action instead. This is configurable with the 'set' action and defaults to 'exec' + +### Git + +You can use the sync command to keep a repo in sync with git. Using basic pull/push on master. +If you want to have more control simply don't use this. +If the repo isn't a git repo yet you will be asked to initialize an empty one and set up remotes. +When quit halfway through this process it's probably better to either start over or just fix it manually. + +Autosyncing is possible, but will do so after every edit or add action. So figure out if you want that yourself. + + + + +%package -n python3-bronotes +Summary: A commandline note organization tool. +Provides: python-bronotes +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-bronotes +# Bronotes + +Basically a wrapper to access notes in a directory on your system anywhere from the commandline. And keep it in sync with git. + +Functionality so far: + * Create a note directory on your system on first start + * Add new notes + * Remove notes + * Move notes and directories around + * Edit notes with your $EDITOR + * List notes dir in a tree + * Generate autocompletions for zsh + * Execute arbitrary commands in the notes directory + * The show and edit actions search for matching notes if no valid path is given + +## Installation + +```bash +$ pip install bronotes +``` + +On first command a folder to be used is asked. + +### Completions + +For now there's no built-in completions. +ZSH completions can be generated so you can place them where needed: +```bash +$ bnote completions | tee ~/.oh-my-zsh/completions/_BRONOTES +``` + +## Usage + +By default this wraps any shell command you feed it and executes it in your notes directory. When using any of the defined actions (see bnote -h) it will do that instead. +The default can be changed, and the regular shell alternatives for actions like 'rm' can be used by just using the 'exec' action manually. + +```bash +$ bnote -h # For actions overview, actions have their own sub help-pages. +``` + +```bash +$ bnote list +.notes/ +|-- baewfweiogn +|-- testblaat.md +|-- blarpblarp.md +``` + +```bash +$ bnote madness # madness is a great way to browse your markdown files in a local server + start the madness + env production + listen 0.0.0.0:3000 +``` + +* Subcommands have their own help pages. +* When using the edit or show subcommand, it falls back on the -s option if the path to your note is not valid. +* If the first argument given is not recognized by bronotes, a default action will be taken and the first argument will be fed to that action instead. This is configurable with the 'set' action and defaults to 'exec' + +### Git + +You can use the sync command to keep a repo in sync with git. Using basic pull/push on master. +If you want to have more control simply don't use this. +If the repo isn't a git repo yet you will be asked to initialize an empty one and set up remotes. +When quit halfway through this process it's probably better to either start over or just fix it manually. + +Autosyncing is possible, but will do so after every edit or add action. So figure out if you want that yourself. + + + + +%package help +Summary: Development documents and examples for bronotes +Provides: python3-bronotes-doc +%description help +# Bronotes + +Basically a wrapper to access notes in a directory on your system anywhere from the commandline. And keep it in sync with git. + +Functionality so far: + * Create a note directory on your system on first start + * Add new notes + * Remove notes + * Move notes and directories around + * Edit notes with your $EDITOR + * List notes dir in a tree + * Generate autocompletions for zsh + * Execute arbitrary commands in the notes directory + * The show and edit actions search for matching notes if no valid path is given + +## Installation + +```bash +$ pip install bronotes +``` + +On first command a folder to be used is asked. + +### Completions + +For now there's no built-in completions. +ZSH completions can be generated so you can place them where needed: +```bash +$ bnote completions | tee ~/.oh-my-zsh/completions/_BRONOTES +``` + +## Usage + +By default this wraps any shell command you feed it and executes it in your notes directory. When using any of the defined actions (see bnote -h) it will do that instead. +The default can be changed, and the regular shell alternatives for actions like 'rm' can be used by just using the 'exec' action manually. + +```bash +$ bnote -h # For actions overview, actions have their own sub help-pages. +``` + +```bash +$ bnote list +.notes/ +|-- baewfweiogn +|-- testblaat.md +|-- blarpblarp.md +``` + +```bash +$ bnote madness # madness is a great way to browse your markdown files in a local server + start the madness + env production + listen 0.0.0.0:3000 +``` + +* Subcommands have their own help pages. +* When using the edit or show subcommand, it falls back on the -s option if the path to your note is not valid. +* If the first argument given is not recognized by bronotes, a default action will be taken and the first argument will be fed to that action instead. This is configurable with the 'set' action and defaults to 'exec' + +### Git + +You can use the sync command to keep a repo in sync with git. Using basic pull/push on master. +If you want to have more control simply don't use this. +If the repo isn't a git repo yet you will be asked to initialize an empty one and set up remotes. +When quit halfway through this process it's probably better to either start over or just fix it manually. + +Autosyncing is possible, but will do so after every edit or add action. So figure out if you want that yourself. + + + + +%prep +%autosetup -n bronotes-2.4.1 + +%build +%py3_build + +%install +%py3_install +install -d -m755 %{buildroot}/%{_pkgdocdir} +if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi +if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi +if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi +if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi +pushd %{buildroot} +if [ -d usr/lib ]; then + find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/lib64 ]; then + find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/bin ]; then + find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/sbin ]; then + find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst +fi +touch doclist.lst +if [ -d usr/share/man ]; then + find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst +fi +popd +mv %{buildroot}/filelist.lst . +mv %{buildroot}/doclist.lst . + +%files -n python3-bronotes -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Wed May 31 2023 Python_Bot <Python_Bot@openeuler.org> - 2.4.1-1 +- Package Spec generated |