| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
o make it be 'use strict' aware
o factorize options managment in one place
- standalone tools :
o they all now support -h|--help -v|--version, ...
o they can add their own options to %standalone::usages
- harddrake : use std --testing/$::testing rather than its own
--test option
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
rationale:
- currently, we use _("xxx") as a shorthand for gettext("xxx"). It
also used to call xgettext with --keyword=_
- alas, function &_ is global and not by package (notice esp. that _
is not exported in common.pm)
- this lead to big ugly pb with packages defining their own &_,
overriding common.pm's &_
- a fix is to set @::textdomains to add a new domain (the default
being "libDrakX")
but relying on the global "_" is still dangerous!
|
| |
|
| |
|
|
|
|
|
| |
(so that 'use strict' works)
|
| |
|
|
|
|
|
|
| |
=> allows to remove the somewhat mythical
$::isEmbedded = ($::XID, $::CCPID) = "@ARGV" =~ /--embedded (\w+) (\w+)/
|
|
|
|
| |
@install_steps_auto_install::graphical_steps
|
| |
|
| |
|
|
|
|
|
|
| |
auto_inst.cfg.pl, replay_install.img) to /root/drakx/,
and also save stage1.log there
|
|
|
|
|
|
|
| |
with nice help from Pixel for the tough Perl part
- move 'use standalone' up in all standalone apps,
to comply to 'explanations'
|
|
|
|
| |
only ?
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
ask_from_entries_refH_powered in ask_from_
|
| |
|
|
- put %installSteps in a separate package (steps.pm) (for drakxtools)
- use additional fields {auto} and {noauto}, by step, to ease interactive auto install and oem stuff
- in install2.pm, perform each step either from the interactive class or from install_steps, according to the {auto} flag
- id, tell each step to not try to be automatic if {noauto}
- in the install, have auto install bootdisk created in install_any so we can always write a bootdisk (from install_steps) for further use from drakautoinst in standalone
- interactive version of install_steps_auto_install is now inheriting from the interactive class, so we can click on a previous automatic step and have it interactively during an interactive auto install
|