Re: [pve-devel] Properties in plugins

2013-10-13 Thread Dietmar Maurer
> And BTW. the two plugins did use the same syntax but never the less the error > was displayed. If you study the code in SectionConfig.pm it does not care > whether the syntax is identical or not it merely checks whether a property has > been defined or not. > 'die "duplicate property" if defined(

Re: [pve-devel] Properties in plugins

2013-10-13 Thread Michael Rasmussen
On Sun, 13 Oct 2013 11:01:27 +0200 Michael Rasmussen wrote: > It was just something I bump into while developing the ZFSPlugin. When > configuring the plugin you need to enter a block size which I naturally > named 'blocksize' but the NexentaPlugin also needing this info and this > plugin also na

Re: [pve-devel] Properties in plugins

2013-10-13 Thread Michael Rasmussen
On Sun, 13 Oct 2013 06:51:06 + Dietmar Maurer wrote: > > What property/plugin do you talk about? > It was just something I bump into while developing the ZFSPlugin. When configuring the plugin you need to enter a block size which I naturally named 'blocksize' but the NexentaPlugin also need

Re: [pve-devel] Properties in plugins

2013-10-12 Thread Dietmar Maurer
> Above failure is displayed if two or more plugins have defined an identical > name > for a property so my question is: Why can a plugin not have a property by the > same name as another plugin? To avoid confusion. If you want the same name, it should have also the same syntax. What property/p

[pve-devel] Properties in plugins

2013-10-12 Thread Michael Rasmussen
Hi Dietmar, I am wondering about the reason for the following: pvedaemonduplicate property at /usr/share/perl5/PVE/SectionConfig.pm line 123 Above failure is displayed if two or more plugins have defined an identical name for a property so my question is: Why can a plugin not have a property by t