Hi,
maybe someone of you reads an opensuse-packaging ML. I started a discussion
about adopting [1] of Fedora Packaging Guidelines for openSUSE.
Benefits are:
- they structure is better than ours
- we could compare a differences between conventions and work on unify
I asked an original author of the documentation, Tom 'spot' Callaway from
RedHat, about it and he respond me that content is under Open Publication
License [2][3], so we can use it as a base for SUSE Packaging Conventions.
I downloaded a content from fedoraproject.org and have two problems:
- Where's api.php for en.opensuse.org wiki? We use a non-standard layout
for wiki and I don't know how to get an access to it. I want to use it for
import and for tracking a changes in pages (it would be useful track and
synchronize changes between wikis).
- Fedora Packaging.* pages contains a ':' as a separator, so you have a
Packaging:Guidelines, instead Packaging/Guidelines - this is not very regular,
but it should helps to avoid possible conflicts.
[1] http://lists.opensuse.org/opensuse-packaging/2009-02/msg00043.html
[2] http://fedoraproject.org/wiki/Legal/Licenses
[3] http://fedoraproject.org/wiki/Legal/Licenses/OPL
Best regards
Michal Vyskocil
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org
I can't view:
http://en.opensuse.org/Portal/All
It comes up as totally blank page, not even parts on the top and left side.
I tried Firefox and Konqueror.
Strange part is that I can edit page, and according to Recent Changes it is
stored although all I get on Preview and Save is internal server error page.
--
Regards, Rajko
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org
On Mittwoch 11 Februar 2009 15:51:02 Michal Vyskocil wrote:
> Or another example - is really necessary talk about BuildService
> account on packaging cookbooks of KDE[5] or Java[6]? In fact with
> this structure, where they exists outside Packaging/ it makes a
> sense, but it's really necessary?
Please "ping" the original authors of the pages you've mentioned.
> So main questions are:
> - how could be Packaging/ maintained (eg. we would have a Docbook
> original somewhere and convert it to wiki as SUSE packaging
NO!
We've a docbook in the past, but writing xml (even with the best editor
in town) is ugly. That's why we use the wiki for it: it's easier to get
people working/fixing things in the wiki than in a separate book stored
in a CVS somewhere else.
But: it might be a good idea to have some tools which extract the wiki
pages from time to time and produce some kind of PDF, static HTML or
something like that for users without internet access.
> conventions [2])? - how could we structure existing information to be
> more readable and useful for community?
=> Should be something for the Wiki Mailingllist, too - CCing...
> - what is missing, or unclear and needs to be improved?
> (- and who will do this all ;-))
>
> [1] http://fedoraproject.org/wiki/Packaging:Guidelines
> [2] http://en.opensuse.org/Packaging/SUSE_Package_Conventions
> [3] http://en.opensuse.org/Packaging/
> [4] https://fedoraproject.org/wiki/Packaging/LicensingGuidelines
> [5] http://en.opensuse.org/KDE/Packaging/Cookbook
> [6] http://en.opensuse.org/Java/Packaging/Cookbook
Regards,
Lars
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org
On Sonntag 01 Februar 2009 22:07:05 Cristian Rodríguez wrote:
> Sascha 'saigkill' Manns escribió:
> RPMLINT gives me any Errors or
>
> > warnings. But these things to fix, are very difficult.
>
> Actually, it is quite the opposite, most rpmlint warnings are very
> simple to fix,
^^^^^^^^ *smile*
> but I understand that new packagers may have a hard
> time with the lack of "real" formal documentation..
Yes it is so.
> > From my side, i can
> > say, that it's not good to make rpmlint as standard in OBS
> it is good, because it provides a "first line of defense" to users,
> so they avoid getting broken packages.
Oh. This sentence was from my old mail. Now (a few weeks ago) i'm
understanding the importance of the rpmlint and the other checks.
> Just wondering.. what error message or warning you fail to understand
> ?
Actually my Knowledge was growed up (thanks to Petr). But in the
Guidelines as we had acknowleged, the Princip is, that we would like to
be (or develop) the easyest and best Distribution. And i think we must
simplify:
* the Graphic System (for the Endusers)
* the development.
Simplifying the development and packaging Process is if we all share our
Knowledge to the whole Community. (My Joy minimized if i every time must
ask for an Explainig RPMLint Error or Warning.) The Wiki (Forums,
Mailnglists and Bugzilla) was a strategic important and a very good
Sign. If we all share our Knowledge, and freeze it in the wiki, every
Community Member can recieve the Informatrions. So we save time, brain,
and the Nerves. Two Persons must not ask the same Question in different
(or same) Medium.
Short Version: If we invest regularly our time, to write or edit
Wikipages, we can share our Informations. If the Information is fixed,
we can access the Information through the Wiki-Serarch Field. That
minimize the Forum and Mailingliststraffic.
Proposal for TODO-List
To updated Wikisites:
*RPMLint
--
Sincereley yours
Sascha Manns
openSUSE Marketing Team (Weekly News)
openSUSE Build Service
Web: http://saschamanns.gulli.to
Blog: http://lizards.opensuse.org/author/saigkill
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org
Hi Folks,
I’m an new Packager in OpenSUSE BuildService, and i like this work. But
if i would like to package for Factory, RPMLINT gives me any Errors or
warnings. But these things to fix, are very difficult. Our Wiki Side for
RPMLINT doesn’t contain many Error or Warningcodes. From my side, i can
say, that it's not good to make rpmlint as standard in OBS, and we have
not enough dokumentation :-(
But yesterday i’ve found an Side, with other Errorcodes from RPMLINT.
Today i imported these Codes to our Wikiside
http://en.opensuse.org/Packaging/RpmLint. I think it is not possible to
list all codes on the Side. But i wish, that the side includes more
Codes in the future.
No i would like to make an Call for contribution. If every Packager
insert the codes, that he knows, we have an good library soon.
And on this Moment i would like to make an request about helping- Thank
you all for the hard Work. And please have an eye on Documentations :-)
--
Sincereley yours
Sascha Manns
openSUSE Marketing Team (Weekly News)
openSUSE Build Service
Web: http://saschamanns.gulli.to
Blog: http://lizards.opensuse.org/author/saigkill
--
To unsubscribe, e-mail: opensuse-wiki+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-wiki+help(a)opensuse.org