Hi,
On 2/26/2006 1:27 PM, Felix Schwarz wrote:
Hi all,
I just noticed that the directive LabelFormat is deprecated in 1.38 -
at least according to the manual:
"Please note that this directive is deprecated and is replaced in
version 1.37 and greater with a Python script for creating volume
names."
Therefore I have two questions:
- What is your policy with deprecated directives?
While I'm not the one to make that decision, I do see some good reasons
why it should be removed. One of them is that it's really too
complicated, the other that it's very often (kind of) misused,
especially in conjunction with disk based backups. Many users create
volume names containing the client name and date of backup and then
wonder why either their disk is running full (when not recycling) or why
the contents of the volumes doesn't fit the name (when recycling and new
data is put into the volumes.
(The most reasonable way to use volume names is, in my opinion, to use
simple names like Tape0001 or Full-0002 and so on and leave the volume
management to Bacula, but that's probably a matter of taste...)
Will you remove
LabelFormat in 1.40?
Again, I can't answer that, but I don't think Kern will remove it as
long as the code around it still is functional. There might be a time
when integrating the LabelFormat function is no longer easy and then, I
guess, it will be removed.
More important, the "deprecated" statement allows all of us who support
Bacula (eiter on the list or commercially) to refuse help with this
topic ;-)
I think Bacula should warn users when they try to
use deprecated directives in order to make them aware of upcoming
changes.
Yes, that's probably right, but the phrase in the manual *could* be
considered enough of a warning... still, seeing a console message might
be useful, but I'd expect that only when removing the function is
determined.
- Why did you chose to deprecate LabelFormat? While I definitely
appreciate the new flexibility with Python scripting, I think
LabelFormat is a very commonly used directive and it is much easier
for simple use cases just to use a directive instead of a Python
script.
Already the third question ;-)
I think I stated my personal opinion above, but I think that using
python events will be more and more common in the future, when the
available events and methods of interaction grow beyond the current
limitation... at the moment, IIRC, setting volume names is almost the
only function implemented that feeds data back to Bacula.
I guess that, once Kern or anybody else finds the time and the
motivation to work on it, the python interface will grow faster.
I could not find any postings related to this topic (but my short
search in the mailing list archives does not qualify as "thorough
searching") so please apologize if this has been brought up earlier.
Well, I don't think this was ever discussed in depth, so I assumed that
nobody was really that much interested in the topic. Or they all decided
they would stay with 1.38 forever :-)
Arno
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
