Bug#985257:

[c***@posteo.jp]

Thank you very much for your report and your idea.

We will take this into account at upstream. Currently there is no open
Issue for that but it is on our internal TODO list.
Please feel free to open an Issue for that:
https://github.com/bit-team/backintime/issues

I would suggest to close this Debian report because it is not highly
related to Debian.

[J. A.]

THX for this thoughtful feature request!

I have added it to the developer's issue tracker:

https://github.com/bit-team/backintime/issues/1331

[c***@posteo.jp]

Hello,

I'm a member of the new upstream maintainer team.

It is not a bug but a feature request. It is still tracked at upstream.
So suggest to close that Debian bug report because it seems not distro
specific.

Kind
Christian Buhtz

[Fabio Fantoni]

Control: forwarded -1 https://github.com/bit-team/backintime/issues/1331

@Christian Buhtz: Is better to keep open until a fix will be released
(before upstream and after in debian upload)

[c***@posteo.jp]

Hello,

I do have a side question regarding to a possible solution of this
issue.
Back In Time (BIT) still have eight example callback scripts in a
separate repo [1]. I plan to integrate them into the primary repo. But I
ask myself where to install them when "./configure && make && sudo make
install" is called?

BIT does look in "~/.config/backintime" for a file named
"user-callback".

I would propose to install the 8 example scripts in this folder with a
naming pattern that backintime does treat them as not active in the
first place.

~./config/user-callback.example.default
~./config/user-callback.example.apt-backup
~./config/user-callback.example.sendmail
~./config/user-callback.example.notify
...

So this scripts would become a part of the "backintime-commen" package.

Is this acceptable for you as Debian Maintainers?

Kind
Christian Buhtz

[1] -- <https://github.com/bit-team/user-callback>

[Jonathan Wiltshire]

Hi,

I do have a side question regarding to a possible solution of this issue.
Back In Time (BIT) still have eight example callback scripts in a separate
repo [1]. I plan to integrate them into the primary repo. But I ask myself
where to install them when "./configure && make && sudo make install" is
called?
BIT does look in "~/.config/backintime" for a file named "user-callback".
I would propose to install the 8 example scripts in this folder with a
naming pattern that backintime does treat them as not active in the first
place.
~./config/user-callback.example.default
~./config/user-callback.example.apt-backup
~./config/user-callback.example.sendmail
~./config/user-callback.example.notify
...
So this scripts would become a part of the "backintime-commen" package.
Is this acceptable for you as Debian Maintainers?

The correct place for these is in /usr/share/doc/<pkg>, at least as far as
Debian is concerned. The package manager has no business touching files in
user home directories and if you build that into upstream, the Debian
packaging will have to work around it.

Cheers,

[c***@posteo.jp]

Hello Franceso,
Hello Jonathan,

please see upstream PR #1899

<https://github.com/bit-team/backintime/pull/1899>

The user-callback example scripts now installed (via make) in
/usr/share/doc/backintime-common/user-callback-examples

This might half fix your ticket.

From the GUI this scripts are not accessible right now.
Currently I don't have a good idea about an elegant solution for the
GUI.
Maybe you can give me some inspiration?

I don't want to provide a text-editor window. I would like to "force"
the users to use there default text editor.
But Back In Time can help them to open one of the example scripts with
that editor.

Best,
Christian

[c***@posteo.jp]

Hello,

upstream maintainer here. Please see this merged upstream PR

<https://github.com/bit-team/backintime/pull/1899>

The user-callback scripts not part of upstream repo, installed in
"/usr/share/doc/backintime-common/user-callback-examples" (via make) and
added to the user manual.

The integration into the GUI is still missing
(https://github.com/bit-team/backintime/issues/1331).

Regards,
Christian Buhtz