Bug 8768 - Syntax Typen der Config-Registry Variablen
Syntax Typen der Config-Registry Variablen
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UCR
UCS 2.0
All Linux
: P4 enhancement (vote)
: ---
Assigned To: Bugzilla Mailingliste
:
Depends on:
Blocks: 4891
  Show dependency treegraph
 
Reported: 2007-07-19 13:31 CEST by Janis Meybohm
Modified: 2014-02-18 21:34 CET (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Further conceptual development
Max CVSS v3 score:


Attachments
Update base/* type=bool (13.84 KB, patch)
2013-09-19 13:21 CEST, Philipp Hahn
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Janis Meybohm univentionstaff 2007-07-19 13:31:54 CEST
Ich würde vorschlagen das man sich, auch wenn sie noch nicht 
verwendet werden, schon mal auf ein paar Syntaxtypen für das Type-Feld 
der Univention Config Registry Variablen einigt. Es wäre z.B. günstig wenn bool, string, int, list jetzt schon eintragen werden könnten, dann müssten zumindest nicht alle Variablen mit der Einführung der Types überarbeitet werden.
Comment 1 Philipp Hahn univentionstaff 2011-05-12 15:18:34 CEST
Siehe auch sie Liste auf <https://hutten.knut.univention.de/mediawiki/index.php/UCR>
Comment 2 Philipp Hahn univentionstaff 2013-09-19 13:21:01 CEST
Created attachment 5446 [details]
Update base/* type=bool
Comment 3 Stefan Gohmann univentionstaff 2014-02-18 21:34:10 CET
This issue has been filed against UCS 2.0.

UCS 2.0 is out of maintenance and many UCS components have vastly changed in
later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug".
In this case please provide detailed information on how this issue is affecting
you.