Il 07/02/2015 14:05, Per Øyvind Karlsen ha scritto:
....
Undocumented features don't get used. In my short experience
what????
In your what experience ? Muhahahahahah , that's really nice
of rpm I have seen countless fragments
beginning with % which I have absolutely no idea what they do.
Now you may say that I should find out :) well one can but the
amount of time spent doing so can be prohibitive.
There's tons of examples spread around in spec files, many people has
succesfully figured them out and adopted them, most of features are
fairly intuitive, and for the trigger implementation it's been
documented for several years under /usr/share/doc/rpm/triggers
(trigger implementation in rpm is nothing new, the only new thing
about it is support for triggering on paths and also triggers for pre-
& posttrans.)
But there is the "dark side of the moon" , too...many people has
successfully figured them out in the very "don't do this to the rpm" way,
by using the template/example specs according to weather or something
very difficult to understand...
While I'm not trying to boast about the large amount of software I
write for this distribution compared to pretty much anyone else, it
does take up a lot of time, time others could contribute their help as
a community efforts on helping writing documentation for the work I
produce.
And as I already said, the examples you'll find in spec files
throughout the distro are fairly self-explanatory, whileas I have no
problem answering questions for anyone who would do the kind effort of
helping out documenting packaging policies, functionality, new
features and what not, along the same lines as for the most content
that the wiki consists of..
If I were to document all policies, new functionality, and what not on
all the software I'm developing in the context of this distro, that
would be an incredibly unfair share of workload..
By comparison, I'm *quite* sure Panu isn't actively documenting
everything relating to rpm on the fedora wiki...
--
Regards.
Per Øyvind
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
I really think that the best way find your own way around packaging is
the old MDV way... I know ,sad but truth...
meaning a senior packager that can follow the newbies development, I
know that we don't have man power for this
but this is the safest and best way to have a new generation of -not
that bad- packagers...
Now you all can jump on my back , but deep inside all old packagers know
very well that
I might have right....
So investing the time in following the new packagers can slow down OMA's
development , for time being, but
instead we can have another Hannula, Wang, Bero, Castro, POK a.s.o. ...
All I'm asking here is how much of your time dedicated to OMA you''ll be
agree to spend in this boring
rising a new generation of packagers?
( It's logical that I'm asking the senior packagers)
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
