Package Details: crestic 1.0.0-2

Git Clone URL: https://aur.archlinux.org/crestic.git (read-only, click to copy)
Package Base: crestic
Description: Configurable restic wrapper
Upstream URL: https://github.com/nils-werner/crestic
Keywords: backup
Licenses: MIT
Submitter: nilsw
Maintainer: nilsw
Last Packager: nilsw
Votes: 5
Popularity: 0.000965
First Submitted: 2020-01-19 10:45 (UTC)
Last Updated: 2023-10-23 13:39 (UTC)

Latest Comments

1 2 Next › Last »

dreieck commented on 2024-07-02 12:39 (UTC) (edited on 2024-07-02 12:39 (UTC) by dreieck)

OK, I also could create a standalone crestic-doc package.

Now I made it a split package, installing the latest development status of crestic:

nilsw commented on 2024-06-18 14:03 (UTC)

Because that package does not exist yet so I can create it.

Yeah, but that's not what -git packages are for... They're for building from the latest VCS revision, not for forking because you'd like to see something implemented but don't want to define what you want and then wait a little bit.

Sounds more like you're looking to pick a fight or find a reason for a fork tbh...

I just install the docs/ directory containing the documentation markdown files into /usr/share/doc/crestic/. Upstream has the docs, they just need to be installed.

Ah, now we're getting somewhere, thanks! I'll look into it.

dreieck commented on 2024-06-18 13:55 (UTC) (edited on 2024-06-18 13:56 (UTC) by dreieck)

I'm confused, how would having a -git version help with docs

Because that package does not exist yet so I can create it.

(OK, I also could create a standalone crestic-doc package.)

Wouldn't it make much more sense to define what you want and then bundle efforts to put it upstream?

I just install the docs/ directory containing the documentation markdown files into /usr/share/doc/crestic/. Upstream has the docs, they just need to be installed.

nilsw commented on 2024-06-18 13:51 (UTC) (edited on 2024-06-18 13:58 (UTC) by nilsw)

I'm confused, how would having a -git version help with docs, if there isn't something like a manpage in upstream? Wouldn't it make much more sense to define what you want and then bundle efforts to put it upstream?

dreieck commented on 2024-06-18 13:24 (UTC) (edited on 2024-06-18 13:54 (UTC) by dreieck)

There is a lot of documentation at https://nils-werner.github.io/crestic/ already, what else would you like to see?

Have it locally, so that it can be consulted offline while developing scripts ;-).

OK, I am going to make a crestic-git package including the documentation.

nilsw commented on 2024-06-18 07:27 (UTC)

Could you be a little bit more precise?

There is a lot of documentation at https://nils-werner.github.io/crestic/ already, what else would you like to see?

dreieck commented on 2024-06-17 21:05 (UTC)

Feature request for the PKGBUILD:

Install documentation (usage and config file) and config file examples.

Regards!

nilsw commented on 2024-04-03 09:40 (UTC)

I'm not using python-setuptools, but python-build and python-installer. If setuptools is missing that dependency should go into one of them.

ishanarora commented on 2024-04-02 23:34 (UTC)

'python-setuptools' is missing from makedepends

nilsw commented on 2023-10-23 13:39 (UTC)

Thanks for the heads up! I've pushed a new pkgrel that adds the dependency.

1 2 Next › Last »