humm.. rolling update ? (easy as kick the word in the round)
an then save a snapshoot of srpm's for 2 years
and make every only updates and the next version only a snapshoot from a
good running compilation.
Bugfixes and updates let direct running in and a repository like Rugyada
have told..
with 3 steps.. goose-bumps, cooker and stable and stable can make from
time to
time an compilation for a distribution and the rpm-installer can use the
3 versions of repository.
and with the stable-packets can make all 1/2 years a snapshot.
and hold them ever up to date as stable and fully fixed and good running
Distribution...
(for Web-Providers and Industrie and so on..) If we have a really stable
and a good running Distribution,
have we are a possible for stand out with an Controllcenter and an
rpm-installer..
and the possible for installing direct from the stable mirrors..
(this is also why we need fast as possible again an rpm-installer)
(by the way control Center.. TPG, why let the QT-MCC not use the
actually configured KDE-Theme
(in colors and iconthemes if exist the icons..in an kde-icontheme ) ?
Hardcoding a theme it's imho crap, because, the User should chose, what
-he- like and not what -we- like..,
every and anywhere press up an stamp not's not every the best.. for this
it exist the Theme for GTK and QT..
in colors and icons.. and the Icons it's an other theme.. but why not
chose also the color&icontheme from qt/kde,
is' more easy then to make an couple more icons, also for the Draktools
.. or if no icons exist in the KDE-icontheme,
the one from the default theme.. as an small suggestion.. but
hard-coding an theme directly
in drakconf and so on, it's a really mistake in my opinion.. let the
peoples choose,
what they like and you can also take a really dark theme too.. at last )
best regards
Blacky
Am 09.02.2016 um 16:40 schrieb Tomasz Gajc:
Why to keep them in yet another place ?
We still provide src.rpm for these in openmandriva2013.0,
openmandriva2014.0 repositories...
2016-02-09 11:39 GMT+01:00 Jean-Claude Vanier <[email protected]
<mailto:[email protected]>>:
I agree with Colin. How heavy are they?
2016-02-09 11:12 GMT+01:00 Colin Close <[email protected]
<mailto:[email protected]>>:
> Hi,
> 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.
> They could be stored on the infra server with little impact.
> Best,
> Colin
>
> On Sunday 07 Feb 2016 23:31:14 Tomasz Paweł Gajc wrote:
>> Hi,
>>
>> in our repositories there are:
>> https://abf.io/openmandriva/distro-doc
>> https://abf.io/openmandriva/howto-html-en
>> https://abf.io/openmandriva/howto-html-*
>>
>> Above packages are very outdated, howto-html are from 2008 and
upstream site
>> is dead www.linuxdoc.org <http://www.linuxdoc.org>
>> distro-doc is 2010 and it was provided by Mandriva.
>> These packages are not installed on any ISO, so basically they
take space on
>> repository, something around 100 MiB per arch.
>>
>> My suggestion is to completely drop these packages.
>>
>>
>
>
> _______________________________________________
> OM-Cooker mailing list
> [email protected] <mailto:[email protected]>
>
http://ml.openmandriva.org/mailman/listinfo/om-cooker_ml.openmandriva.org
_______________________________________________
OM-Cooker mailing list
[email protected] <mailto:[email protected]>
http://ml.openmandriva.org/mailman/listinfo/om-cooker_ml.openmandriva.org
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/mailman/listinfo/om-cooker_ml.openmandriva.org
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/mailman/listinfo/om-cooker_ml.openmandriva.org
