<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
humm.. rolling update ? (easy as kick the word in the round)<br>
an then save a snapshoot of srpm's for 2 years <br>
and make every only updates and the next version only a snapshoot
from a good running compilation.<br>
Bugfixes and updates let direct running in and a repository like
Rugyada have told..<br>
with 3 steps.. goose-bumps, cooker and stable and stable can make
from time to <br>
time an compilation for a distribution and the rpm-installer can use
the 3 versions of repository.<br>
and with the stable-packets can make all 1/2 years a snapshot. <br>
and hold them ever up to date as stable and fully fixed and good
running Distribution...<br>
(for Web-Providers and Industrie and so on..) If we have a really
stable and a good running Distribution,<br>
have we are a possible for stand out with an Controllcenter and an
rpm-installer..<br>
and the possible for installing direct from the stable mirrors.. <br>
(this is also why we need fast as possible again an rpm-installer)<br>
<br>
(by the way control Center.. TPG, why let the QT-MCC not use the
actually configured KDE-Theme <br>
(in colors and iconthemes if exist the icons..in an kde-icontheme )
? <br>
Hardcoding a theme it's imho crap, because, the User should chose,
what -he- like and not what -we- like.., <br>
every and anywhere press up an stamp not's not every the best.. for
this it exist the Theme for GTK and QT..<br>
in colors and icons.. and the Icons it's an other theme.. but why
not chose also the color&icontheme from qt/kde, <br>
is' more easy then to make an couple more icons, also for the
Draktools .. or if no icons exist in the KDE-icontheme, <br>
the one from the default theme.. as an small suggestion.. but
hard-coding an theme directly <br>
in drakconf and so on, it's a really mistake in my opinion.. let the
peoples choose, <br>
what they like and you can also take a really dark theme too.. at
last )<br>
<br>
best regards<br>
Blacky<br>
<br>
<div class="moz-cite-prefix">Am 09.02.2016 um 16:40 schrieb Tomasz
Gajc:<br>
</div>
<blockquote class=" cite"
id="mid_CAEkne_oxjFhq7PuEv2jAWzOYwxzb_osP2uNmj85Pk05A9E3HcQ_mail_gmail_com"
cite="mid:CAEkne-oxjFhq7PuEv2jAWzOYwxzb=osP2uNmj85Pk05A9E3HcQ@mail.gmail.com"
type="cite">
<div dir="ltr">
<div>Why to keep them in yet another place ?<br>
</div>
<div> We still provide src.rpm for these in openmandriva2013.0,
openmandriva2014.0 repositories...<br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2016-02-09 11:39 GMT+01:00 Jean-Claude
Vanier <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jclvanier@gmail.com" target="_blank">jclvanier@gmail.com</a>></span>:<br>
<blockquote id="Cite_8152261" class="gmail_quote cite"
style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">I agree with Colin. How heavy are
they?<br>
<div>
<div class="h5"><br>
2016-02-09 11:12 GMT+01:00 Colin Close <<a
moz-do-not-send="true"
href="mailto:itchka@compuserve.com"><a class="moz-txt-link-abbreviated" href="mailto:itchka@compuserve.com">itchka@compuserve.com</a></a>>:<br>
> Hi,<br>
> I don't have a problem with removing them from the
repository but I do wonder whether they should be
archived somewhere. The reason? I hav written quite few
manuals in my time and I have found thsat it is much
easier to get the job done if you have a template. Yes
the content is out of date or just plain wrong but the
headings and sub-headings give a very good idea of what
needs to be written.<br>
> They could be stored on the infra server with
little impact.<br>
> Best,<br>
> Colin<br>
><br>
> On Sunday 07 Feb 2016 23:31:14 Tomasz Paweł Gajc
wrote:<br>
>> Hi,<br>
>><br>
>> in our repositories there are:<br>
>> <a moz-do-not-send="true"
href="https://abf.io/openmandriva/distro-doc"
rel="noreferrer" target="_blank">https://abf.io/openmandriva/distro-doc</a><br>
>> <a moz-do-not-send="true"
href="https://abf.io/openmandriva/howto-html-en"
rel="noreferrer" target="_blank">https://abf.io/openmandriva/howto-html-en</a><br>
>> <a moz-do-not-send="true"
href="https://abf.io/openmandriva/howto-html-*"
rel="noreferrer" target="_blank">https://abf.io/openmandriva/howto-html-*</a><br>
>><br>
>> Above packages are very outdated, howto-html
are from 2008 and upstream site<br>
>> is dead <a moz-do-not-send="true"
href="http://www.linuxdoc.org" rel="noreferrer"
target="_blank">www.linuxdoc.org</a><br>
>> distro-doc is 2010 and it was provided by
Mandriva.<br>
>> These packages are not installed on any ISO, so
basically they take space on<br>
>> repository, something around 100 MiB per arch.<br>
>><br>
>> My suggestion is to completely drop these
packages.<br>
>><br>
>><br>
><br>
><br>
</div>
</div>
> _______________________________________________<br>
> OM-Cooker mailing list<br>
> <a moz-do-not-send="true"
href="mailto:OM-Cooker@ml.openmandriva.org">OM-Cooker@ml.openmandriva.org</a><br>
> <a moz-do-not-send="true"
href="http://ml.openmandriva.org/mailman/listinfo/om-cooker_ml.openmandriva.org"
rel="noreferrer" target="_blank">http://ml.openmandriva.org/mailman/listinfo/om-cooker_ml.openmandriva.org</a><br>
<br>
_______________________________________________<br>
OM-Cooker mailing list<br>
<a moz-do-not-send="true"
href="mailto:OM-Cooker@ml.openmandriva.org">OM-Cooker@ml.openmandriva.org</a><br>
<a moz-do-not-send="true"
href="http://ml.openmandriva.org/mailman/listinfo/om-cooker_ml.openmandriva.org"
rel="noreferrer" target="_blank">http://ml.openmandriva.org/mailman/listinfo/om-cooker_ml.openmandriva.org</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OM-Cooker mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OM-Cooker@ml.openmandriva.org">OM-Cooker@ml.openmandriva.org</a>
<a class="moz-txt-link-freetext" href="http://ml.openmandriva.org/mailman/listinfo/om-cooker_ml.openmandriva.org">http://ml.openmandriva.org/mailman/listinfo/om-cooker_ml.openmandriva.org</a>
</pre>
</blockquote>
<br>
<br>
</body>
</html>