https://wiki.archlinux.org/api.php?action=feedcontributions&user=Neotuli&feedformat=atomArchWiki - User contributions [en]2024-03-29T08:01:40ZUser contributionsMediaWiki 1.41.0https://wiki.archlinux.org/index.php?title=TU_Meeting&diff=53221TU Meeting2008-11-12T07:13:39Z<p>Neotuli: </p>
<hr />
<div>This page was created to schedule TU meetings.<br />
<br />
Next meeting can be at:<br />
<br />
* 15/16 November<br />
* 22/23 November<br />
* 29/30 November<br />
<br />
And we should discuss the results of the pkgstats script and the direction for the [community] repo.<br />
<br />
'''Please, add your name below and the time/day that fits best for you.'''<br />
<br />
'''Please specify your availability in GMT.'''<br />
<br />
<br />
{|<br />
|-<br />
|style="font-weight: bold;padding-right:50px"|Nick<br />
|style="font-weight: bold;padding-right:70px"|15-16 Nov<br />
|style="font-weight: bold;padding-right:70px"|22-23 Nov<br />
|style="font-weight: bold;padding-right:70px;"|29-30 Nov<br />
|style="font-weight: bold;"|GMT<br />
|-<br />
|Hugo (hdoria)||Cant||Any Time||Any Time||GMT-3<br />
|-<br />
|Daenyth||Daytime/early night||Daytime/early night||Daytime/early night||GMT-5<br />
|-<br />
|ElasticDog||Any Time on Sunday||Can't||Any Time on Sunday||GMT-5<br />
|-<br />
|abhidg||Sat 1100-1730, Sun 0330-1730||Sun 0330-1730||Sun 0330-1730||GMT<br />
|-<br />
|angvp||Cant||night||night||GMT+1<br />
|-<br />
|foutrelis||Cant||8:00 - 16:00 ||Cant||EET (is this GMT+2?)<br />
|-<br />
|firmicus||Sun 19-23||19-23||19-23||GMT<br />
|-<br />
|louipc||16 Nov: 1400-||Any Time||Any Time||GMT<br />
|-<br />
|Ronald (pressh) || 15Nov:night;16Nov daytime/early night || 23Nov:daytime/early night || 30Nov:afternoon-night || GMT+1<br />
|-<br />
|BaSh || *-23 or 04-* || *-23 or 04-* || *-23 or 04-* || GMT+1<br />
|-<br />
|Partition || 13-20 || 13-20 || 13-20 || GMT+1<br />
|-<br />
|sergej || 20+ || 20+ || 20+ || GMT+3<br />
|-<br />
|Kessia (even)||Cant||Maybe||Any Time||GMT-3<br />
|-<br />
|gummibaerchen||Any Time||Any Time||Any Time||UTC+1 // CET<br />
|-<br />
|Neverth||Cant||11-21||11-21||GMT+2<br />
|-<br />
|StefanHusmann||Any Time||Any Time||Any Time||GMT+1<br />
|-<br />
|Simo (neotuli)||Cant||Any Time||Any Time||GMT-6<br />
|}</div>Neotulihttps://wiki.archlinux.org/index.php?title=TU_Meeting&diff=53220TU Meeting2008-11-12T07:13:24Z<p>Neotuli: </p>
<hr />
<div>This page was created to schedule TU meetings.<br />
<br />
Next meeting can be at:<br />
<br />
* 15/16 November<br />
* 22/23 November<br />
* 29/30 November<br />
<br />
And we should discuss the results of the pkgstats script and the direction for the [community] repo.<br />
<br />
'''Please, add your name below and the time/day that fits best for you.'''<br />
<br />
'''Please specify your availability in GMT.'''<br />
<br />
<br />
{|<br />
|-<br />
|style="font-weight: bold;padding-right:50px"|Nick<br />
|style="font-weight: bold;padding-right:70px"|15-16 Nov<br />
|style="font-weight: bold;padding-right:70px"|22-23 Nov<br />
|style="font-weight: bold;padding-right:70px;"|29-30 Nov<br />
|style="font-weight: bold;"|GMT<br />
|-<br />
|Hugo (hdoria)||Cant||Any Time||Any Time||GMT-3<br />
|-<br />
|Daenyth||Daytime/early night||Daytime/early night||Daytime/early night||GMT-5<br />
|-<br />
|ElasticDog||Any Time on Sunday||Can't||Any Time on Sunday||GMT-5<br />
|-<br />
|abhidg||Sat 1100-1730, Sun 0330-1730||Sun 0330-1730||Sun 0330-1730||GMT<br />
|-<br />
|angvp||Cant||night||night||GMT+1<br />
|-<br />
|foutrelis||Cant||8:00 - 16:00 ||Cant||EET (is this GMT+2?)<br />
|-<br />
|firmicus||Sun 19-23||19-23||19-23||GMT<br />
|-<br />
|louipc||16 Nov: 1400-||Any Time||Any Time||GMT<br />
|-<br />
|Ronald (pressh) || 15Nov:night;16Nov daytime/early night || 23Nov:daytime/early night || 30Nov:afternoon-night || GMT+1<br />
|-<br />
|BaSh || *-23 or 04-* || *-23 or 04-* || *-23 or 04-* || GMT+1<br />
|-<br />
|Partition || 13-20 || 13-20 || 13-20 || GMT+1<br />
|-<br />
|sergej || 20+ || 20+ || 20+ || GMT+3<br />
|-<br />
|Kessia (even)||Cant||Maybe||Any Time||GMT-3<br />
|-<br />
|gummibaerchen||Any Time||Any Time||Any Time||UTC+1 // CET<br />
|-<br />
|Neverth||Cant||11-21||11-21||GMT+2<br />
|-<br />
|StefanHusmann||Any Time||Any Time||Any Time||GMT+1<br />
|Simo (neotuli)||Cant||Any Time||Any Time||GMT-6<br />
|}</div>Neotulihttps://wiki.archlinux.org/index.php?title=AUR_Translation&diff=46952AUR Translation2008-08-03T18:38:22Z<p>Neotuli: /* Updating an Existing Translation */</p>
<hr />
<div>[[Category:Package development (English)]]<br />
[[Category:HOWTOs (English)]]<br />
<br />
:''This document describes how to create and maintain AUR translations.''<br />
:''All you need is yourself, git, and python.''<br />
<br />
=Creating a New Translation=<br />
Before beginning, please make sure that git and python are installed. Also, please do not translate if you are unwilling to maintain or find someone to maintain the translation. This is due to the fact that the AUR is a rapidly evolving project and there are constantly new strings to be translated appearing. If the translations get too out of sync with the released versions, there will be too many untranslated strings for the translation to be usable, and it will have to be removed or disabled.<br />
<br />
* Check out the AUR source using git.<br />
$ git clone http://projects.archlinux.org/git/aur.git aur-git<br />
* Go into the AUR source and run translation_tool. translation_tool will interactively guide you through the translation process, simply answer its questions and prompts. If you wish to stop at some point during the translation, you may kill translation_tool using Ctrl+C. If you later wish to continue the translation, simply run translation_tool again, and it will continue from where you left off.<br />
$ cd aur-git<br />
$ git checkout -b testing origin/testing<br />
$ cd web<br />
$ utils/translation_tool<br />
* To commit your patch to your branch:<br />
$ git add <all edited files><br />
$ git commit -s<br />
* Send the gzipped patch to either Simo (simo.archlinux.org) or to Aur-Dev ML for inclusion in the AUR.<br />
$ git format-patch origin/master<br />
<br />
=Updating an Existing Translation=<br />
<br />
* Update your copy of the AUR code.<br />
$ cd aur-git<br />
$ git pull<br />
* Run translation_tool, which will only prompt for strings that have changed or been added since the last translation.<br />
$ cd web<br />
$ utils/translation_tool<br />
* To commit your patch to your branch:<br />
$ git add <all edited files><br />
$ git commit -s<br />
* Send the gzipped patch to the Aur-Dev ML (aur-dev.archlinux.org) for inclusion in the AUR.<br />
$ git format-patch origin/master</div>Neotulihttps://wiki.archlinux.org/index.php?title=User:Neotuli&diff=43239User:Neotuli2008-06-18T13:32:35Z<p>Neotuli: Replacing page with '__NOEDITSECTION__
==Developer Roadmap==
=== World Domination ===
{{progressbar|38}}'</p>
<hr />
<div>__NOEDITSECTION__<br />
==Developer Roadmap==<br />
<br />
=== World Domination ===<br />
{{progressbar|38}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=DeveloperWiki:ArchlinuxOrg_Services&diff=43238DeveloperWiki:ArchlinuxOrg Services2008-06-18T13:31:06Z<p>Neotuli: /* Current Services */</p>
<hr />
<div>This is a list of basic sites and services we provide at archlinux.org, their status, and any outstanding concerns people have had with them.<br />
<br />
== Current Services ==<br />
<br />
* Main Site<br />
** Provides: News, Repo Listings, Out of date reporting, developer wiki, developer information, donation information, documentation<br />
** Audience: everyone<br />
** Status: operational<br />
** Issues: none, documentation has few contributors and falls out of date easily<br />
<br />
* Forums<br />
** Provides: place to discuss anything arch related, and even non-arch related, general announcements<br />
** Audience: starting point for newer users, few older users, some non-users. Most people seem to start here and gravitate away over time.<br />
** Status: operational<br />
** Issues: none<br />
<br />
* Wiki<br />
** Provides: user-based documentation, tutorials, etc<br />
** Audience: newer users, many older users<br />
** Status: operational<br />
** Issues: none<br />
<br />
* Bug Tracker<br />
** Provides: place to report distro-centric problems directly to developers<br />
** Audience: everyone<br />
** Status: operational<br />
** Issues: none<br />
<br />
* AUR<br />
** Provides: Central repository for user-contributed PKGBUILDs, managment for community repo<br />
** Audience: TUs and more experienced users who are able to create and maintain pkgbuilds.<br />
** Status: operational, with many known issues, slow development<br />
** Issues: Codebase is messy and hard to work with. Slow development but rapid growth of userbase. Klunky interface.<br />
<br />
* Mailing Lists<br />
** Provide: Place to discuss everything arch-related, including the distro, development, pacman, aur, and porting. Generally very on-topic.<br />
** Audience: Users who wish to discuss those particular topics. Usually slightly more experienced users and those inclined to use email.<br />
** Status: operational<br />
** Issues: none<br />
<br />
* IRC channels<br />
** Provide: Live dicussion about arch, arch development, and localized dicussion. Often other topics as well.<br />
** Audience: Full range of users, often those who are IRC-inclined.<br />
** Status: operational<br />
** Issues: none<br />
<br />
* Planet Arch<br />
** Provides: aggregation of arch-related blogs and feeds<br />
** Audience: unsure<br />
** Status: operational<br />
** Issues: poor visibility, tracks very old entries leading to large page size<br />
<br />
* Package Repositories<br />
** Provides: Basic and expanded package sets for the distro. FTP for little-used direct access. Rsync for mirroring access.<br />
** Audience: all users<br />
** Status: operational<br />
** Issues: bandwidth is a limiting factor when large upgrades occur, leads to mirror sync issues<br />
<br />
* Revision Control - CVS, SVN, GIT<br />
** Provides: Tracking for PKGBUILDs, arch site, scripts and related projects<br />
** Audience: developers, advanced users<br />
** Status: operational<br />
** Issues: CVS migration needs to be finished.<br />
<br />
* Newsletter<br />
** Provides: Concise aggreggation of arch related activity over small timespans.<br />
** Audience: everyone<br />
** Status: biweekly releases<br />
** Issues: none<br />
<br />
== Removed Services ==<br />
<br />
* Development Blog<br />
** Provided: place to post arch development related items that are not quite front page newsworthy. Place for some community projects to post updates<br />
** Status: Removed<br />
** Issues: poor visibility, and little use<br />
** Replaced by: Forum announcement section, which has been integrated into the planet feeds.<br />
<br />
* Arch Artwork Gallery<br />
** Provided: place for users to post screenshots and arch-related images<br />
** Status: Removed<br />
** Issues: poor visibility, little use<br />
** Replaced by: Nothing. The users historically used the forum for screenshot threads, and free image hosting sites. This trend continues.<br />
<br />
* Pastebin<br />
** Provides: Place to share snippets of text<br />
** Audience: mostly IRC users, but pretty much anyone<br />
** Status: Removed<br />
** Issues: Spam issues. It was little used.</div>Neotulihttps://wiki.archlinux.org/index.php?title=Package_Maintainer_guidelines&diff=34982Package Maintainer guidelines2008-01-13T10:54:21Z<p>Neotuli: /* Accessing the Repo */</p>
<hr />
<div>[[Category:Package management (English)]]<br />
[[Category:About Arch (English)]]<br />
[[Category:Guidelines (English)]]<br />
{{Article summary start}}<br />
{{Article summary text|Explains Arch User Repository's Trusted Users.}}<br />
{{Article summary heading|Available in languages}}<br />
{{i18n_entry|English|AUR Trusted User Guidelines}}<br />
{{i18n_entry|简体中文|AUR Trusted User 导引}}<br />
{{Article summary heading|Related articles}}<br />
{{Article summary wiki|AUR Q & A}}<br />
{{Article summary wiki|AUR User Guidelines}}<br />
{{Article summary wiki|AUR}}<br />
{{Article summary end}}<br />
<br />
=The Trusted User (TU)=<br />
The '''Trusted User (TU)''' is a member of the community charged with<br />
keeping the AUR in working order. He/she maintains popular packages, and<br />
votes in administrative matters. A TU is elected from active community<br />
members by current TUs in a democratic process. TUs are the only<br />
members who have a final say in the direction of the AUR.<br />
<br />
The TUs are governed using the [http://dev.archlinux.org/~simo/TUbylaws.html TU bylaws]<br />
<br />
==TU Duties==<br />
===The TU and UNSUPPORTED===<br />
<br />
The TUs should also make an effort to check package submissions in UNSUPPORTED for malicious code and good PKGBUILDing standards. In around 80% of cases the PKGBUILDs in the UNSUPPORTED are very simple and can be quickly checked for sanity and malicious code by the TU team.<br />
<br />
TUs should also check PKGBUILDs for minor mistakes, suggest corrections and improvements. The TU should endeavor to confirm that all pkgs follow the Arch Packaging Guidelines/Standards and in doing so share their skills with other package builders in an effort to raise the standard of package building across the distro.<br />
<br />
TUs are also in an excellent position to document recommended practices.<br />
<br />
===="Flag Safe" guidelines====<br />
There is new functionality in the AUR that will allow TUs to mark pkgs as checked. However, users are still responsible for checking the PKGBUILDs themselves.<br />
<br />
===The TU and [community], Guidelines for Package Maintenance===<br />
<br />
==== Accessing the Repo ====<br />
<br />
Follow these instructions for uploading/modifying packages once you have become a TU:<br />
<ol><br />
<br />
<li>Install the "aurtools" package. Make sure you read the [[AURtools Tutorial]]</li><br />
<li>You will need to email your the output of "htpasswd -n" to whoever is in charge of the AUR CVS repo ( Simo Leone <simoATarchlinuxDOTorg> ). It comes with Apache.</li><br />
htpasswd -n <userid><br />
<li>Run the following commands to checkout the AUR CVS:<br><br />
<pre><br />
export CVSROOT=":pserver:<userid>@cvs.archlinux.org:/home/cvs-community"<br />
cvs login<br />
cvs co community</pre></li><br />
<br />
<li> To add a new package:</li><br />
<pre><br />
cvs add &lt;directory&gt;<br />
cd &lt;directory&gt;<br />
cvs add PKGBUILD<br />
</pre><br />
<li>Make a commit:</li><br />
cvs commit<br />
<li> To upload a binary package:</li><br />
Please note that AUR password is to be used with tupkg (NOT the CVS password)<br />
tupkg --user &lt;userid&gt; --password &lt;aur-password&gt; &lt;packagefile.pkg.tar.gz&gt;<br />
<br />
<li> After uploading a package and committing the build files, tag the files with this command:</li><br />
cvs tag -cFR CURRENT &lt;newpackagebuilddir&gt;<br />
Package changes become available on every full and half of hour. Verify everything was uploaded properly, then select the newly added or updated package in the web interface and set yourself as the maintainer.<br />
</ol><br />
<i>'''Note:''' Steps 5-7 can be run with communitypkg in one command as mentioned below in the AURtools tutorial.</i><br />
<br />
<br />
<i><br />
'''Note:''' In some cases, especially for community packages, an x86_64 TU might bump the pkgrel by .1 (and not +1). This indicates that the <strong> change to the PKGBUILD is x86_64 specific </strong> and i686 <br />
maintainers <strong> should not </strong> rebuild the package for i686. When the TU decides to bump the pkgrel , it should be done with the usual increment of +1. However, a previous pkgrel=2.1 must <br />
not become pkgrel=3.1 when bumped by the TU and must instead be pkgrel=3. In a nutshell, leave dot (.) releases exclusive to the x86_64 TU's to avoid confusion.<br />
</i><br />
<br />
==== Uploading packages to x86_64-version of community ====<br />
* step 1 till 5 are the same as mentioned above.<br />
* when using tupkg add "--port 1035" to the list of parameters<br />
* Tag the package with "cvs tag -cFR CURRENT-64"<br />
<br />
==== Adopting Packages ====<br />
A TU may adopt any package at any time. But because the TU's time is<br />
limited, he should try to only adopt popular packages. The voting<br />
mechanism in the AUR allows a TU to quickly gauge which packages users<br />
want.<br />
<br />
A maintainer should adopt his selected package(s) via the web interface. That maintainer is then responsible for bug fixes and new version updates. Packages must be properly cleaned and fixed after adoption.<br />
<br />
==== Disowning packages ====<br />
You can disown packages by choosing "Disown Packages" in the AUR webinterface.<br />
If a TU can't or doesn't want to maintain a package any longer, a<br />
notice should be posted to the AUR Mailing List, so another TU can<br />
maintain it. A package can still be disowned even if no other TU wants<br />
to maintain it, but the TUs should try not to drop many packages (they<br />
shouldn't take on more than they have time for). If a package has<br />
become obsolete or isn't used any longer, it can be removed completely<br />
as well.<br />
<br />
If a package has been removed completely, it can be uploaded once again<br />
(fresh) to UNSUPPORTED, where a regular user can maintain the package<br />
instead of the TU.<br />
<br />
==== Deleting packages from [community] ====<br />
<br />
Removing a package from [community] is easy but not straightforward.<br />
After you've removed it from community, you could re-add it to <br />
unsupported (make sure to keep a copy!) and orphan it, for adoption by <br />
some other user in unsupported.<br />
<br />
To remove a package, all you really need to do is remove the CURRENT (and possibly CURRENT-64) tag <br />
from the PKGBUILD. You do this by doing:<br />
<br />
cvs tag -d CURRENT PKGBUILD<br />
cvs tag -d CURRENT-64 PKGBUILD<br />
<br />
If you wish to remove the package materials from CVS for future <br />
revisions (because you don't want the old stuff lying around), you can <br />
do the following '''FROM THE PACKAGE'S DIRECTORY''' in your checked out <br />
version of the community repo (this is very important!):<br />
<br />
cd /path/to/<packagedirname><br />
cvs tag -dl CURRENT #or CURRENT-64<br />
cvs rm -fl<br />
cvs commit<br />
<br />
'''BE VERY CAREFUL''' with CVS delete commands! By untagging current on the whole repo you risk removing '''EVERYTHING''' in [community]. I've suggested commands that hope to minimize that possibility, but there's <br />
still danger where delete is involved. Especially note that the tag <br />
delete takes '''IMMEDIATELY''' before committing, so be very careful.<br />
<br />
Also, due to weirdness of CVS, actually removing the package directory <br />
is impossible. It will still show up in a checked out version unless you set up a ~/.cvsrc file that will help prune empty directories. The following is helpful:<br />
<br />
cvs -q<br />
diff -uN<br />
rdiff -u<br />
checkout -P<br />
update -dP<br />
<br />
Any TU can remove any package in [community] so keep this in mind and be <br />
extra super careful with this ability, lest you accidentally wipe out <br />
someone else's package.<br />
<br />
=== AURtools ===<br />
To help the Trusted Users with their duties, the AURtools were written based on the '''tupkg''' tool. If you are Trusted User, it is highly recommended that you use the AURtools. The [[AURtools Tutorial]] was written to help you to get used to them.</div>Neotulihttps://wiki.archlinux.org/index.php?title=Template:Merge&diff=30700Template:Merge2007-10-11T20:42:47Z<p>Neotuli: Protected "Template:Merge" [edit=sysop:move=sysop]</p>
<hr />
<div>{{Message_box|<br />
id = merge|<br />
backgroundcolor = beige|<br />
signalcolor = beige|<br />
signal = [[Image:Tango-two-arrows.png]]|<br />
heading = This article is a candidate for merging.|<br />
message = It has been suggested that this page or section be [[Wikipedia:Merging and moving pages|merged]] with ''[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]''. ([[{{{2|:{{NAMESPACE}} talk:{{PAGENAMEE}}}}}|Discuss]]) }}<br />
<includeonly>[[Category:Articles For Merge|{{PAGENAME}}]]</includeonly></div>Neotulihttps://wiki.archlinux.org/index.php?title=Template:Merge&diff=30698Template:Merge2007-10-11T20:38:42Z<p>Neotuli: Unprotected "Template:Merge"</p>
<hr />
<div>{{Message_box|<br />
id = merge|<br />
backgroundcolor = beige|<br />
signalcolor = beige|<br />
signal = [[Image:Tango-two-arrows.png]]|<br />
heading = This article is a candidate for merging.|<br />
message = It has been suggested that this page or section be [[Wikipedia:Merging and moving pages|merged]] with ''[[:{{NAMESPACE}}:{{{1}}}|{{{1}}}]]''. ([[{{{2|:{{NAMESPACE}} talk:{{PAGENAMEE}}}}}|Discuss]]) }}<br />
[[Category:Articles For Merge|{{PAGENAME}}]]</div>Neotulihttps://wiki.archlinux.org/index.php?title=Template:Translateme&diff=30697Template:Translateme2007-10-11T20:38:30Z<p>Neotuli: Protected "Template:Translateme" [edit=sysop:move=sysop]</p>
<hr />
<div>{{Message_box|<br />
id = translateme|<br />
backgroundcolor = beige|<br />
signalcolor = beige|<br />
signal = [[Image:Tango-preferences-desktop-locale.png]]|<br />
heading = This page (or parts of it) was marked to be translated.|<br />
message = If you speak the original and target languages of the page, feel free to finish the translation. After you have finished the translation, remove the <nowiki>{{translateme}}</nowiki> flag from the document. }}<br />
<includeonly>[[Category:Translation Requested|{{PAGENAME}}]]</includeonly></div>Neotulihttps://wiki.archlinux.org/index.php?title=Template:Deletion&diff=30696Template:Deletion2007-10-11T20:38:23Z<p>Neotuli: Protected "Template:Deletion" [edit=sysop:move=sysop]</p>
<hr />
<div>{{Message_box|<br />
id = deletion|<br />
backgroundcolor = beige|<br />
signalcolor = beige|<br />
signal = [[Image:Tango-user-trash-full.png]]|<br />
heading = This article is being considered for deletion.|<br />
message = This article is being considered for deletion. This typically means that it is too short, written too poorly to be helpful, or not relevant to Arch Linux. ([[:{{NAMESPACE}} talk:{{PAGENAME}}|Discuss]]) }}<br />
<includeonly>[[Category:Articles For Deletion|{{PAGENAME}}]]</includeonly></div>Neotulihttps://wiki.archlinux.org/index.php?title=Template:Translateme&diff=30693Template:Translateme2007-10-11T20:34:04Z<p>Neotuli: Unprotected "Template:Translateme"</p>
<hr />
<div>{{Message_box|<br />
id = translateme|<br />
backgroundcolor = beige|<br />
signalcolor = beige|<br />
signal = [[Image:Tango-preferences-desktop-locale.png]]|<br />
heading = This page (or parts of it) was marked to be translated.|<br />
message = If you speak the original and target languages of the page, feel free to finish the translation. After you have finished the translation, remove the <nowiki>{{translateme}}</nowiki> flag from the document. }}<br />
[[Category:Translation Requested|{{PAGENAME}}]]</div>Neotulihttps://wiki.archlinux.org/index.php?title=Template:Deletion&diff=30692Template:Deletion2007-10-11T20:33:26Z<p>Neotuli: Unprotected "Template:Deletion"</p>
<hr />
<div>{{Message_box|<br />
id = deletion|<br />
backgroundcolor = beige|<br />
signalcolor = beige|<br />
signal = [[Image:Tango-user-trash-full.png]]|<br />
heading = This article is being considered for deletion.|<br />
message = This article is being considered for deletion. This typically means that it is too short, written too poorly to be helpful, or not relevant to Arch Linux. ([[:{{NAMESPACE}} talk:{{PAGENAME}}|Discuss]]) }}<br />
[[Category:Articles For Deletion|{{PAGENAME}}]]</div>Neotulihttps://wiki.archlinux.org/index.php?title=ArchWiki:News&diff=27438ArchWiki:News2007-07-30T04:13:49Z<p>Neotuli: </p>
<hr />
<div>[[Category:About Arch (English)]]<br />
[[Category:General (English)]]<br />
{{News|07/30/2007 - Wiki upgrade|<br />
Wiki was upgraded tonight, I tested a bit, but not extensively. Get a hold of me if I broke something.|<br />
--[[User:Neotuli|simo]] 00:13, 30 July 2007 (EDT)<br />
}}<br />
{{News|03/02/2007 - New Wiki Skin|<br />
I've changed the wiki skin to the one used over at http://wiki.archlinuxfr.org (and formerly used on the german community's site). It is much less cluttered than the previous skin and fits the theme on the rest of our pages better. Enjoy.|--[[User:Neotuli|simo]] 15:53, 2 March 2007 (EST)<br />
}}<br />
{{News|01/21/2007 - Wiki upgrade|<br />
The mediawiki running Archwiki has been upgraded. Please report any issues on the [[ArchWiki:Bug_reports|bug report page]].|<br />
--[[User:Neotuli|simo]] 19:47, 21 January 2007 (PST)<br />
}}<br />
{{News|11/13/2006 - Wiki restructuring| <br />
We officially announce the start of grand wiki restructuring. The project is coordinated by [[User:Dusty|Dusty]], [[User:Foxbunny|foxbunny]], and [[User:Tardo|tardo]]. Project details are constantly updated on the [[Priority Todo]] page. Contact any of [[ContactList|these people]] if you want to participate in the project.|<br />
--[[User:Foxbunny|foxbunny]] 08:26, 13 November 2006 (PST)<br />
}}<br />
<br />
{{News|07/24/2005 - Wiki Migration is done!| <br />
The Great Wiki Migration has come to and end. There are still a few pages that need migration, but they are translation pages (language in other languages). You can find a link for them off the migration page locate at [[Migration Chunks!]]|<br />
--[[User:Cactus|cactus]] 15:49, 24 Jul 2005 (EDT)<br />
}}<br />
<br />
{{News|07/17/2005 - ArchWiki rolls again| <br />
The ArchLinux Wiki is alive again! Look for lots of new content to spring forth, as the Wiki will hopefully perform better, and be easier to use.|<br />
--[[User:Cactus|cactus]] 05:17, 17 Jul 2005 (EDT)<br />
}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=User:Neotuli&diff=25064User:Neotuli2007-05-30T06:18:04Z<p>Neotuli: </p>
<hr />
<div>__NOEDITSECTION__<br />
==Developer Roadmap==<br />
<br />
=== AUR 1 ===<br />
* Routine maintenance and hot fixes<br />
* Keep TUs happy<br />
=== [[AUR 2]] ===<br />
{{progressbar|1}}<br />
* Short public brainstorm session - complete<br />
* Design with main site merge in mind - in progress<br />
* Code the damn thing - not started<br />
<br />
=== Pacbuild ===<br />
{{progressbar|66}}<br />
* Add unionfs support<br />
* apple memory consumption on pkg upload<br />
<br />
=== ArchStats ===<br />
* Routine maintenance<br />
{{progressbar|0}}<br />
* Possible overhaul w/ cooler/faster web interface - in planning<br />
<br />
=== Web Stuff ===<br />
==== www.archlinux.org ====<br />
* Implement cvsweb links to testing packages<br />
* add #archlinux64 to http://www.archlinux.org/irc/<br />
* 0.8 Release updates<br />
** Metalinks<br />
** Docs<br />
* Fix news ordering so that order_by isn't used everywhere.<br />
==== bbs.archlinux.org ====<br />
{{progressbar|100}}<br />
* punBB migration<br />
* Routine maintenance<br />
* Spam control<br />
==== wiki.archlinux.org ====<br />
* Routine maintenance<br />
* Spam control<br />
==== bugs.archlinux.org ====<br />
* Get jabber notification working<br />
==== art.archlinux.org ====<br />
* Replace gallery with something cooler? <br />
** http://www.zenphoto.org/zenphoto/ ?<br />
==== blog.archlinux.org ====<br />
* Do we even need this? Possibly get rid of.<br />
==== pastebin.archlinux.org ====<br />
* Possibly change software, this one does a couple annoying things.<br />
<br />
=== World Domination ===<br />
{{progressbar|38}}<br />
<br />
<br />
=== Other Random Stuff ===<br />
* Improve staging upload structure...<br />
* extrapkg should upload to hidden, issue mv over ssh, (check for another file of same name though),updater can be automated now</div>Neotulihttps://wiki.archlinux.org/index.php?title=User:Neotuli&diff=23903User:Neotuli2007-05-09T22:20:44Z<p>Neotuli: </p>
<hr />
<div>__NOEDITSECTION__<br />
==Developer Roadmap==<br />
<br />
=== AUR 1 ===<br />
* Routine maintenance and hot fixes<br />
* Keep TUs happy<br />
=== [[AUR 2]] ===<br />
{{progressbar|1}}<br />
* Short public brainstorm session - complete<br />
* Design with main site merge in mind - in progress<br />
* Code the damn thing - not started<br />
<br />
=== Pacbuild ===<br />
{{progressbar|66}}<br />
* Add unionfs support<br />
* apple memory consumption on pkg upload<br />
<br />
=== ArchStats ===<br />
* Routine maintenance<br />
{{progressbar|0}}<br />
* Possible overhaul w/ cooler/faster web interface - in planning<br />
<br />
=== Web Stuff ===<br />
==== www.archlinux.org ====<br />
* Implement cvsweb links to testing packages<br />
* add #archlinux64 to http://www.archlinux.org/irc/<br />
* 0.8 Release updates<br />
** Metalinks<br />
** Docs<br />
* Fix news ordering so that order_by isn't used everywhere.<br />
==== bbs.archlinux.org ====<br />
{{progressbar|100}}<br />
* punBB migration<br />
* Routine maintenance<br />
* Spam control<br />
==== wiki.archlinux.org ====<br />
* Routine maintenance<br />
* Spam control<br />
==== bugs.archlinux.org ====<br />
* Get jabber notification working<br />
==== art.archlinux.org ====<br />
* Replace gallery with something cooler? <br />
** http://www.zenphoto.org/zenphoto/ ?<br />
==== blog.archlinux.org ====<br />
* Do we even need this? Possibly get rid of.<br />
==== pastebin.archlinux.org ====<br />
* Possibly change software, this one does a couple annoying things.<br />
<br />
=== World Domination ===<br />
{{progressbar|38}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=User:Neotuli&diff=22707User:Neotuli2007-04-08T02:13:25Z<p>Neotuli: </p>
<hr />
<div>__NOEDITSECTION__<br />
==Developer Roadmap==<br />
<br />
=== AUR 1 ===<br />
* Routine maintenance and hot fixes<br />
* Keep TUs happy<br />
=== [[AUR 2]] ===<br />
{{progressbar|1}}<br />
* Short public brainstorm session - complete<br />
* Design with main site merge in mind - in progress<br />
* Code the damn thing - not started<br />
<br />
=== Pacbuild ===<br />
{{progressbar|66}}<br />
* Add unionfs support<br />
* apple memory consumption on pkg upload<br />
<br />
=== ArchStats ===<br />
* Routine maintenance<br />
{{progressbar|0}}<br />
* Possible overhaul w/ cooler/faster web interface - in planning<br />
<br />
=== Web Stuff ===<br />
==== www.archlinux.org ====<br />
* Implement cvsweb links to testing packages<br />
* add #archlinux64 to http://www.archlinux.org/irc/<br />
* 0.8 Release updates<br />
** Metalinks<br />
** Docs<br />
==== bbs.archlinux.org ====<br />
{{progressbar|100}}<br />
* punBB migration<br />
* Routine maintenance<br />
* Spam control<br />
==== wiki.archlinux.org ====<br />
* Routine maintenance<br />
* Spam control<br />
==== bugs.archlinux.org ====<br />
* Get jabber notification working<br />
==== art.archlinux.org ====<br />
* Replace gallery with something cooler? <br />
** http://www.zenphoto.org/zenphoto/ ?<br />
==== blog.archlinux.org ====<br />
* Do we even need this? Possibly get rid of.<br />
==== pastebin.archlinux.org ====<br />
* Possibly change software, this one does a couple annoying things.<br />
<br />
=== World Domination ===<br />
{{progressbar|38}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=Bug_Day/2010&diff=22692Bug Day/20102007-04-07T16:41:23Z<p>Neotuli: /* Website */</p>
<hr />
<div>{{stub}}<br />
<br />
We have 23 pages of reports for Arch Linux project in Flyspray. :(<br />
<br />
Here I tried to list and categorize some old reports.<br />
<br />
= Installer =<br />
* [http://bugs.archlinux.org/task/1224 FR #1224] - partially implemented, addons are needed<br />
<br />
= System =<br />
* [http://bugs.archlinux.org/task/1186 BR #1186] - a compromise solution could be made<br />
* [http://bugs.archlinux.org/task/3601 FR #3601] - decision?<br />
* [http://bugs.archlinux.org/task/3941 FR #3941] - patch provided<br />
<br />
==== status? ====<br />
* [http://bugs.archlinux.org/task/2505 BR #2505] - anacron and fcron are in community<br />
* [http://bugs.archlinux.org/task/2829 BR #2829]<br />
* [http://bugs.archlinux.org/task/2977 FR #2977]<br />
<br />
= Packages =<br />
* [http://bugs.archlinux.org/task/2727 FR #2727] - fixed on x86_64, release updated package on i686<br />
* [http://bugs.archlinux.org/task/2775 BR #2775] - still not fixed (is it worth to fix?)<br />
* [http://bugs.archlinux.org/task/3365 BR #3365] - shouldn't be an issue<br />
* [http://bugs.archlinux.org/task/3810 FR #3810] - in my newly created [http://wiki.archlinux.org/index.php/User:Romashka TODO] now<br />
* [http://bugs.archlinux.org/task/4100 FR #4100] - it would be nice to have it be done, there won't be new versions anyway<br />
<br />
==== decision? ====<br />
* [http://bugs.archlinux.org/task/3330 FR #3330]<br />
* [http://bugs.archlinux.org/task/3691 BR #3691] - fix provided<br />
* [http://bugs.archlinux.org/task/3743 BR #3743]<br />
* [http://bugs.archlinux.org/task/3944 BR #3944]<br />
* [http://bugs.archlinux.org/task/4064 FR #4064] - I propose to close as "Won't implement"<br />
<br />
==== status? ====<br />
* [http://bugs.archlinux.org/task/2451 BR #2451]<br />
* [http://bugs.archlinux.org/task/3765 BF #3765]<br />
* [http://bugs.archlinux.org/task/3948 BR #3948]<br />
* [http://bugs.archlinux.org/task/4079 BR #4079]<br />
* [http://bugs.archlinux.org/task/4090 BR #4090]<br />
<br />
==== trivial fixes ====<br />
* [http://bugs.archlinux.org/task/2893 BR #2893]<br />
* [http://bugs.archlinux.org/task/2904 BR #2904]<br />
* [http://bugs.archlinux.org/task/3602 BR #3602]<br />
* [http://bugs.archlinux.org/task/3758 BR #3758]<br />
* [http://bugs.archlinux.org/task/3992 BR #3992]<br />
* [http://bugs.archlinux.org/task/4051 FR #4051]<br />
<br />
= Website =<br />
* [http://bugs.archlinux.org/task/2290 FR #2290] - trivial to implement<br />
* [http://bugs.archlinux.org/task/3986 FR #3986] - not much harder<br />
* [http://bugs.archlinux.org/task/4116 BR #4116] - annoys too much people :) - also annoying to implement, lots of special cases<br />
<br />
= Pacman =<br />
No promises on fixing these on bug day, but if any of the pacman devs or ML readers are around these would be good candidates to look at, especially if you like C and shell script coding more than fixing the above bugs. :)<br />
<br />
* [http://bugs.archlinux.org/task/6404 #6404] - remote downloads via -U/-A should be stored in /tmp instead<br />
* [http://bugs.archlinux.org/task/6604 #6604] - srcpac needs updates for pacman3 (as well as a general sprucing)<br />
* [http://bugs.archlinux.org/task/3556 #3556] - test to see if this is closable<br />
* [http://bugs.archlinux.org/task/6057 #6057] - write a pactest for this, investigate all issues described there<br />
* [http://bugs.archlinux.org/task/6437 #6437] - someone good with wchar output in C should take a look<br />
* [http://bugs.archlinux.org/task/6791 #6791] - easy patch attached<br />
* [http://bugs.archlinux.org/task/4099 #4099] - it's in contrib now</div>Neotulihttps://wiki.archlinux.org/index.php?title=User:Neotuli&diff=22537User:Neotuli2007-04-04T06:20:51Z<p>Neotuli: </p>
<hr />
<div>__NOEDITSECTION__<br />
==Developer Roadmap==<br />
<br />
=== AUR 1 ===<br />
* Routine maintenance and hot fixes<br />
* Keep TUs happy<br />
=== [[AUR 2]] ===<br />
{{progressbar|1}}<br />
* Short public brainstorm session - complete<br />
* Design with main site merge in mind - in progress<br />
* Code the damn thing - not started<br />
<br />
=== Pacbuild ===<br />
{{progressbar|66}}<br />
* Add unionfs support<br />
* apple memory consumption on pkg upload<br />
<br />
=== ArchStats ===<br />
* Routine maintenance<br />
{{progressbar|0}}<br />
* Possible overhaul w/ cooler/faster web interface - in planning<br />
<br />
=== Web Stuff ===<br />
==== www.archlinux.org ====<br />
* Implement cvsweb links to testing packages<br />
* add #archlinux64 to http://www.archlinux.org/irc/<br />
* 0.8 Release updates<br />
** Metalinks<br />
** Docs<br />
==== bbs.archlinux.org ====<br />
{{progressbar|100}}<br />
* punBB migration<br />
* Routine maintenance<br />
* Spam control<br />
==== wiki.archlinux.org ====<br />
* Routine maintenance<br />
* Spam control<br />
==== bugs.archlinux.org ====<br />
* Upgrade Flyspray to 0.9.9.1 [http://flyspray.org/changelog]<br />
* Make interface more intuitive<br />
* Get jabber notification working<br />
==== art.archlinux.org ====<br />
* Replace gallery with something cooler? <br />
** http://www.zenphoto.org/zenphoto/ ?<br />
==== blog.archlinux.org ====<br />
* Do we even need this? Possibly get rid of.<br />
==== pastebin.archlinux.org ====<br />
* Possibly change software, this one does a couple annoying things.<br />
<br />
=== World Domination ===<br />
{{progressbar|38}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=Main_page&diff=22503Main page2007-04-02T06:32:53Z<p>Neotuli: Reverted edits by Toofishes (Talk); changed back to last version by Neotuli</p>
<hr />
<div>__NOTOC__ __NOEDITSECTION__<br />
{{Navigate_i18n_mainpages}}<br />
Welcome to the [[ArchLinux]] Wiki. If you are new to Arch, you may be interested in the [[Beginners Guide]]. Otherwise, dig right in.<br />
<br />
==== &nbsp;&nbsp;[[:Category: About Arch (English)|About Arch]] ====<br />
: [[The Arch Way]] :: [[Arch vs Others]] :: [[FAQ]] :: [[Official Repositories]] :: [[ArchLinux User-community Repository (AUR)|Arch User Repository (AUR)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category: Getting and installing Arch (English)|Getting and Installing Arch]] ====<br />
: [[Official Arch Linux Install Guide|Official Install Guide]] :: [[Post Installation Tips]] :: [[Configuring network|Configuring Network]]<br />
<br />
==== &nbsp;&nbsp;[[:Category: System administration (English)|System Administration]] ====<br />
: [[Pacman]] :: [[:Category: Package management (English)|Package Management]] :: [[Xorg7|Xorg Setup]] :: [[:Category: Desktop environments (English)|Desktop Environments]] :: [[ALSA Setup]]<br />
<br />
==== &nbsp;&nbsp;[[:Category: Desktop user's guide (English)|Desktop User's Guide]] ====<br />
: [[:Category: Internet and Email (English)|Internet and Email]] :: [[:Category: Office (English)|Office]] :: [[:Category: Audio/Video (English)|Audio/Video]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:System recovery (English)|System Recovery]] ====<br />
: [[Reinstalling GRUB]] :: [[Kernel Panics]]<br />
<br />
==== &nbsp;&nbsp;[[:Category: Arch Development (English)|Arch Development]] ====<br />
<br />
==== &nbsp;&nbsp;[[:Category:Arch64 (English)|Arch64]] ====<br />
: [[Arch64 FAQ]]<br />
<br />
==== &nbsp;&nbsp;[[:Category: Live Arch systems (English)|Live Arch Systems]] ====<br />
:: &nbsp;<br />
<br />
== Wiki News ==<br />
<br />
Check the [[Wiki News]] page for the latest lowdown on the Wiki.<br />
<br />
Note that we are currently in the process of editing the wiki structure. If you have some time to make minor or major edits, take a look at the [[Priority Todo]] and the [[WikiTodo]] pages to see how you can help. We're especially interested in having people recategorize the non-English pages. Please coordinate your activities with [[ContactList|admins and sysops]] or [[ArchWiki maintainers (English)|maintainers]].<br />
<br />
== In Your Language ==<br />
More comfortable reading articles in your own language? Browse the categories for the following languages: <br />
: [[:Category:English|English]] :: [[:Category:Česky|Česky]] :: [[:Category:Deutsch|Deutsch]] :: [[:Category:Français|Français]] :: [[:Category:Italiano|Italiano]] :: [[:Category:Polski|Polski]] :: [[:Category:Русский|Русский]] :: [[:Category:Српски|Српски]] :: [[:Category:ไทย|ไทย]]<br />
<br />
== Help ==<br />
If you're having trouble finding what you're looking for, try using the search box to the left.<br />
<br />
You must create an account to edit this wiki. Once done, you can play around in the [[Sandbox]] or your user page to familiarize yourself with ArchWiki markup. The available syntax is listed in the [[:Category:Help|Wiki Help Category]] and there is an [[:Category:ArchWiki Tools (English)|Archwiki Tools section]] with some HOWTOs and guidelines.</div>Neotulihttps://wiki.archlinux.org/index.php?title=User:Neotuli&diff=22495User:Neotuli2007-04-01T18:02:05Z<p>Neotuli: </p>
<hr />
<div>__NOEDITSECTION__<br />
==Developer Roadmap==<br />
<br />
=== AUR 1 ===<br />
* Routine maintenance and hot fixes<br />
* Keep TUs happy<br />
=== [[AUR 2]] ===<br />
{{progressbar|1}}<br />
* Short public brainstorm session - complete<br />
* Design with main site merge in mind - in progress<br />
* Code the damn thing - not started<br />
<br />
=== Pacbuild ===<br />
{{progressbar|66}}<br />
* Add unionfs support<br />
* apple memory consumption on pkg upload<br />
<br />
=== ArchStats ===<br />
* Routine maintenance<br />
{{progressbar|0}}<br />
* Possible overhaul w/ cooler/faster web interface - in planning<br />
<br />
=== Web Stuff ===<br />
==== www.archlinux.org ====<br />
* Implement cvsweb links to testing packages<br />
* 0.8 Release updates<br />
** Metalinks<br />
** Docs<br />
** Torrents<br />
==== bbs.archlinux.org ====<br />
{{progressbar|100}}<br />
* punBB migration<br />
* Routine maintenance<br />
* Spam control<br />
==== wiki.archlinux.org ====<br />
* Routine maintenance<br />
* Spam control<br />
==== bugs.archlinux.org ====<br />
* Upgrade Flyspray to 0.9.9.1 [http://flyspray.org/changelog]<br />
* Make interface more intuitive<br />
* Get jabber notification working<br />
==== art.archlinux.org ====<br />
* Replace gallery with something cooler? <br />
** http://www.zenphoto.org/zenphoto/ ?<br />
==== blog.archlinux.org ====<br />
* Do we even need this? Possibly get rid of.<br />
==== pastebin.archlinux.org ====<br />
* Possibly change software, this one does a couple annoying things.<br />
<br />
=== World Domination ===<br />
{{progressbar|38}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=User:Neotuli&diff=22421User:Neotuli2007-03-30T08:15:53Z<p>Neotuli: </p>
<hr />
<div>__NOEDITSECTION__<br />
==Developer Roadmap==<br />
<br />
=== AUR 1 ===<br />
* Routine maintenance and hot fixes<br />
* Keep TUs happy<br />
=== [[AUR 2]] ===<br />
{{progressbar|1}}<br />
* Short public brainstorm session - complete<br />
* Design with main site merge in mind - in progress<br />
* Code the damn thing - not started<br />
<br />
=== Pacbuild ===<br />
{{progressbar|66}}<br />
* Add unionfs support<br />
* apple memory consumption on pkg upload<br />
<br />
=== ArchStats ===<br />
* Routine maintenance<br />
{{progressbar|0}}<br />
* Possible overhaul w/ cooler/faster web interface - in planning<br />
<br />
=== Web Stuff ===<br />
==== www.archlinux.org ====<br />
* Implement cvsweb links to testing packages<br />
* 0.8 Release updates<br />
** Metalinks<br />
** Docs<br />
** Torrents<br />
==== bbs.archlinux.org ====<br />
{{progressbar|100}}<br />
* punBB migration<br />
* Routine maintenance<br />
* Spam control<br />
==== wiki.archlinux.org ====<br />
* Routine maintenance<br />
* Spam control<br />
==== bugs.archlinux.org ====<br />
* Upgrade Flyspray to 0.9.9.1 [http://flyspray.org/changelog]<br />
* Make interface more intuitive<br />
* Get jabber notification working<br />
==== art.archlinux.org ====<br />
* Replace gallery with something cooler? <br />
** http://www.zenphoto.org/zenphoto/ ?<br />
==== blog.archlinux.org ====<br />
* Do we even need this? Possibly get rid of.<br />
==== pastebin.archlinux.org ====<br />
* Possibly change software, this one does a couple annoying things.<br />
<br />
=== World Domination ===<br />
{{progressbar|35}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=User:Neotuli&diff=22360User:Neotuli2007-03-28T18:52:29Z<p>Neotuli: fixed dev todo lists!</p>
<hr />
<div>__NOEDITSECTION__<br />
==Developer Roadmap==<br />
<br />
=== AUR 1 ===<br />
* Routine maintenance and hot fixes<br />
* Keep TUs happy<br />
=== [[AUR 2]] ===<br />
{{progressbar|1}}<br />
* Short public brainstorm session - complete<br />
* Design with main site merge in mind - in progress<br />
* Code the damn thing - not started<br />
<br />
=== Pacbuild ===<br />
{{progressbar|66}}<br />
* Add unionfs support<br />
* apple memory consumption on pkg upload<br />
<br />
=== ArchStats ===<br />
* Routine maintenance<br />
{{progressbar|0}}<br />
* Possible overhaul w/ cooler/faster web interface - in planning<br />
<br />
=== Web Stuff ===<br />
==== www.archlinux.org ====<br />
* Implement cvsweb links to testing packages<br />
==== bbs.archlinux.org ====<br />
{{progressbar|100}}<br />
* punBB migration<br />
* Routine maintenance<br />
* Spam control<br />
==== wiki.archlinux.org ====<br />
* Routine maintenance<br />
* Spam control<br />
==== bugs.archlinux.org ====<br />
* Upgrade Flyspray to 0.9.9.1 [http://flyspray.org/changelog]<br />
* Make interface more intuitive<br />
* Get jabber notification working<br />
==== art.archlinux.org ====<br />
* Replace gallery with something cooler? <br />
** http://www.zenphoto.org/zenphoto/ ?<br />
==== blog.archlinux.org ====<br />
* Do we even need this? Possibly get rid of.<br />
==== pastebin.archlinux.org ====<br />
* Possibly change software, this one does a couple annoying things.<br />
<br />
=== World Domination ===<br />
{{progressbar|35}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=User:Neotuli&diff=22339User:Neotuli2007-03-27T15:51:46Z<p>Neotuli: </p>
<hr />
<div>__NOEDITSECTION__<br />
==Developer Roadmap==<br />
<br />
=== AUR 1 ===<br />
* Routine maintenance and hot fixes<br />
* Keep TUs happy<br />
=== [[AUR 2]] ===<br />
{{progressbar|1}}<br />
* Short public brainstorm session - complete<br />
* Design with main site merge in mind - in progress<br />
* Code the damn thing - not started<br />
<br />
=== Pacbuild ===<br />
{{progressbar|66}}<br />
* Add unionfs support<br />
* apple memory consumption on pkg upload<br />
<br />
=== ArchStats ===<br />
* Routine maintenance<br />
{{progressbar|0}}<br />
* Possible overhaul w/ cooler/faster web interface - in planning<br />
<br />
=== Web Stuff ===<br />
==== www.archlinux.org ====<br />
* Implement cvsweb links to testing packages<br />
* Fix todo lists<br />
==== bbs.archlinux.org ====<br />
{{progressbar|100}}<br />
* punBB migration<br />
* Routine maintenance<br />
* Spam control<br />
==== wiki.archlinux.org ====<br />
* Routine maintenance<br />
* Spam control<br />
==== bugs.archlinux.org ====<br />
* Upgrade Flyspray to 0.9.9.1 [http://flyspray.org/changelog]<br />
* Make interface more intuitive<br />
* Get jabber notification working<br />
==== art.archlinux.org ====<br />
* Replace gallery with something cooler? <br />
** http://www.zenphoto.org/zenphoto/ ?<br />
==== blog.archlinux.org ====<br />
* Do we even need this? Possibly get rid of.<br />
==== pastebin.archlinux.org ====<br />
* Possibly change software, this one does a couple annoying things.<br />
<br />
=== World Domination ===<br />
{{progressbar|35}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=User:Neotuli&diff=22267User:Neotuli2007-03-26T07:24:07Z<p>Neotuli: </p>
<hr />
<div>__NOEDITSECTION__<br />
==Developer Roadmap==<br />
<br />
=== AUR 1 ===<br />
* Routine maintenance and hot fixes<br />
* Keep TUs happy<br />
=== [[AUR 2]] ===<br />
{{progressbar|1}}<br />
* Short public brainstorm session - complete<br />
* Design with main site merge in mind - in progress<br />
* Code the damn thing - not started<br />
<br />
=== Pacbuild ===<br />
{{progressbar|66}}<br />
* Add unionfs support<br />
* apple memory consumption on pkg upload<br />
<br />
=== ArchStats ===<br />
* Routine maintenance<br />
{{progressbar|0}}<br />
* Possible overhaul w/ cooler/faster web interface - in planning<br />
<br />
=== Web Stuff ===<br />
==== www.archlinux.org ====<br />
* Implement cvsweb links to testing packages<br />
==== bbs.archlinux.org ====<br />
{{progressbar|100}}<br />
* punBB migration<br />
* Routine maintenance<br />
* Spam control<br />
==== wiki.archlinux.org ====<br />
* Routine maintenance<br />
* Spam control<br />
==== bugs.archlinux.org ====<br />
* Upgrade Flyspray to 0.9.9.1 [http://flyspray.org/changelog]<br />
* Make interface more intuitive<br />
* Get jabber notification working<br />
==== art.archlinux.org ====<br />
* Replace gallery with something cooler? <br />
** http://www.zenphoto.org/zenphoto/ ?<br />
==== blog.archlinux.org ====<br />
* Do we even need this? Possibly get rid of.<br />
==== pastebin.archlinux.org ====<br />
* Possibly change software, this one does a couple annoying things.<br />
<br />
=== World Domination ===<br />
{{progressbar|35}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=User:Neotuli&diff=22263User:Neotuli2007-03-26T07:13:50Z<p>Neotuli: </p>
<hr />
<div>__NOEDITSECTION__<br />
==Developer Roadmap==<br />
<br />
=== AUR 1 ===<br />
* Routine maintenance and hot fixes<br />
* Keep TUs happy<br />
=== [[AUR 2]] ===<br />
{{progressbar|1}}<br />
* Short public brainstorm session - complete<br />
* Design with main site merge in mind - in progress<br />
* Code the damn thing - not started<br />
<br />
=== Pacbuild ===<br />
{{progressbar|66}}<br />
* Add unionfs support<br />
* apple memory consumption on pkg upload<br />
<br />
=== ArchStats ===<br />
* Routine maintenance<br />
{{progressbar|0}}<br />
* Possible overhaul w/ cooler/faster web interface - in planning<br />
<br />
=== Web Stuff ===<br />
==== www.archlinux.org ====<br />
* Implement cvsweb links to testing packages<br />
==== bbs.archlinux.org ====<br />
{{progressbar|100}}<br />
* punBB migration<br />
* Routine maintenance<br />
* Spam control<br />
==== wiki.archlinux.org ====<br />
* Routine maintenance<br />
* Spam control<br />
==== art.archlinux.org ====<br />
* Replace gallery with something cooler? <br />
** http://www.zenphoto.org/zenphoto/ ?<br />
==== blog.archlinux.org ====<br />
* Do we even need this? Possibly get rid of.<br />
==== pastebin.archlinux.org ====<br />
* Possibly change software, this one does a couple annoying things.<br />
<br />
=== World Domination ===<br />
{{progressbar|35}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=User:Neotuli&diff=22260User:Neotuli2007-03-26T06:54:38Z<p>Neotuli: </p>
<hr />
<div>__NOEDITSECTION__<br />
==Developer Roadmap==<br />
<br />
=== AUR 1 ===<br />
* Routine maintenance and hot fixes<br />
* Keep TUs happy<br />
=== [[AUR 2]] ===<br />
{{progressbar|1}}<br />
* Short public brainstorm session - complete<br />
* Design with main site merge in mind - in progress<br />
* Code the damn thing - not started<br />
<br />
=== Pacbuild ===<br />
{{progressbar|66}}<br />
* Add unionfs support<br />
* apple memory consumption on pkg upload<br />
<br />
=== ArchStats ===<br />
* Routine maintenance<br />
{{progressbar|0}}<br />
* Possible overhaul w/ cooler/faster web interface - in planning<br />
<br />
=== Web Stuff ===<br />
==== www.archlinux.org ====<br />
* Implement cvsweb links to testing packages<br />
==== bbs.archlinux.org ====<br />
{{progressbar|100}}<br />
* punBB migration<br />
* Routine maintenance<br />
* Spam control<br />
==== wiki.archlinux.org ====<br />
* Routine maintenance<br />
* Spam control<br />
<br />
=== World Domination ===<br />
{{progressbar|35}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=User:Neotuli&diff=22259User:Neotuli2007-03-26T06:47:24Z<p>Neotuli: </p>
<hr />
<div>__NOEDITSECTION__<br />
==Developer Roadmap==<br />
<br />
=== AUR 1 ===<br />
* Routine maintenance and hot fixes<br />
* Keep TUs happy<br />
=== [[AUR 2]] ===<br />
{{progressbar|1}}<br />
* Short public brainstorm session - complete<br />
* Design with main site merge in mind - in progress<br />
* Code the damn thing - not started<br />
<br />
=== Pacbuild ===<br />
{{progressbar|66}}<br />
* Add unionfs support<br />
<br />
=== ArchStats ===<br />
* Routine maintenance<br />
{{progressbar|0}}<br />
* Possible overhaul w/ cooler/faster web interface - in planning<br />
<br />
=== Web Stuff ===<br />
==== www.archlinux.org ====<br />
* Implement cvsweb links to testing packages<br />
==== bbs.archlinux.org ====<br />
{{progressbar|100}}<br />
* punBB migration<br />
* Routine maintenance<br />
* Spam control<br />
==== wiki.archlinux.org ====<br />
* Routine maintenance<br />
* Spam control<br />
<br />
=== World Domination ===<br />
{{progressbar|35}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=User:Neotuli&diff=22258User:Neotuli2007-03-26T06:45:57Z<p>Neotuli: Dev Roadmap</p>
<hr />
<div>==Developer Roadmap==<br />
<br />
=== AUR 1 ===<br />
* Routine maintenance and hot fixes<br />
* Keep TUs happy<br />
=== [[AUR 2]] ===<br />
{{progressbar|1}}<br />
* Short public brainstorm session - complete<br />
* Design with main site merge in mind - in progress<br />
* Code the damn thing - not started<br />
<br />
=== Pacbuild ===<br />
{{progressbar|66}}<br />
* Add unionfs support<br />
<br />
=== ArchStats ===<br />
* Routine maintenance<br />
{{progressbar|0}}<br />
* Possible overhaul w/ cooler/faster web interface - in planning<br />
<br />
=== Web Stuff ===<br />
==== www.archlinux.org ====<br />
* Implement cvsweb links to testing packages<br />
==== bbs.archlinux.org ====<br />
{{progressbar|100}}<br />
* punBB migration<br />
* Routine maintenance<br />
* Spam control<br />
==== wiki.archlinux.org ====<br />
* Routine maintenance<br />
* Spam control<br />
<br />
=== World Domination ===<br />
{{progressbar|35}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=Template:Deletion&diff=22245Template:Deletion2007-03-26T05:41:56Z<p>Neotuli: spellcheck rocks</p>
<hr />
<div>{{Message_box|<br />
id = deletion|<br />
backgroundcolor = beige|<br />
signalcolor = beige|<br />
signal = [[Image:Fairytale Trash Questionmark.png|48px]]|<br />
heading = This article is being considered for deletion.|<br />
message = This article is being considered for deletion. This typically means that it is too short, written too poorly to be helpful, or not relevant to Arch Linux. ([[:{{NAMESPACE}} talk:{{PAGENAME}}|Discuss]]) }}<br />
[[Category:Articles For Deletion|{{PAGENAME}}]]</div>Neotulihttps://wiki.archlinux.org/index.php?title=Template:Deletion&diff=22244Template:Deletion2007-03-26T05:41:27Z<p>Neotuli: reworded</p>
<hr />
<div>{{Message_box|<br />
id = deletion|<br />
backgroundcolor = beige|<br />
signalcolor = beige|<br />
signal = [[Image:Fairytale Trash Questionmark.png|48px]]|<br />
heading = This article is being considered for deletion.|<br />
message = This article is being considered for deletion. This typically means that it is too short, written too poorly to be helpful, or not relevent to Arch Linux. ([[:{{NAMESPACE}} talk:{{PAGENAME}}|Discuss]]) }}<br />
[[Category:Articles For Deletion|{{PAGENAME}}]]</div>Neotulihttps://wiki.archlinux.org/index.php?title=Frequently_asked_questions&diff=21975Frequently asked questions2007-03-16T22:07:11Z<p>Neotuli: Grammar (oh my.. I cant spell) fix.</p>
<hr />
<div>[[Category:About Arch (English)]]<br />
[[Category:FAQs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|FAQ}}<br />
{{i18n_entry|Español|FAQ_(Español)}}<br />
{{i18n_entry|Nederlands|FAQ_(Nederlands)}}<br />
{{i18n_entry|Français|FAQ (Français)}}<br />
{{i18n_entry|Polski|FAQ (Polski)}}<br />
{{i18n_entry|简体中文|FAQ常见问题集}}<br />
{{i18n_entry|Slovensky|FAQ_(Slovensky)}}<br />
{{i18n_entry|Česky|FAQ_(Česky)}}<br />
{{i18n_entry|Deutsch|FAQ_(Deutsch)}}<br />
{{i18n_entry|Português do Brasil|FAQ_(Português do Brasil)}}<br />
{{i18n_entry|Русский|FAQ_(Русский)}}<br />
{{i18n_entry|ไทย|FAQ_(ไทย)}}<br />
{{i18n_links_end}}<br />
<br />
Besides the questions covered below, you may find [[The Arch Way]],[[ArchLinux]], and [[Devland]] helpful. All three contain a good deal of information about ArchLinux.<br />
<br />
= General =<br />
<br />
==Q) I am a complete Linux beginner. Should I use Arch?==<br />
'''A)''' This question has had much debate. Arch is targeted at more advanced Linux users, but some people feel "Arch is a good place to start". If you are a beginner and want to use Arch, just be warned that you MUST be willing to learn. Before asking any question, do your own independent research by googling, searching the Wiki, and searching the forum (and reading past FAQs). If you do that, you should be fine. Also know that many people do not want to answer the same basic questions over and over, so you are exposing yourself to that environment. There is a reason these resources were created/made available to you. You could reference the [[ArchLinux Newbie Guide]]<br />
<br />
==Q) When will the new release be made?==<br />
'''A)''' Arch Linux releases are quite infrequent, and usually only happen when a major change has been made to the installer or something has happened that makes it difficult to run ''pacman -Syu'' to update from the previous release.<br />
<br />
Releases are not terribly important in Arch, because the so-called 'rolling release' system makes new releases out of date as soon as a package has been updated. If you are looking to obtain the latest Arch Linux release, you do not need to reinstall. You simply run the ''pacman -Syu'' command and your system will be identical to what you would get with a brand new install.<br />
<br />
For this same reason, new Arch Linux releases are not typically full of new and exciting features. New and exciting features are released as needed with the packages that are updated, and can be obtained immediately via ''pacman -Syu''<br />
<br />
<br />
==Q) Arch needs more/less press (ie advertisement)==<br />
'''A)''' Arch gets plenty of press as it is. The goal of ArchLinux is not to be large. The goal is to be well done. Let growth occur naturally. Trying to force it to grow too quickly will just cause problems.<br />
<br />
Similarly, do not try to restrict the natural growth. More users might mean more devs to work on ArchLinux. This may cause some organizational issues at the "top", but those will be dealt with when they arrive.<br />
<br />
==Q) Arch needs more documentation==<br />
'''A)'''This is essentially true, so feel free to contribute. Documentation does not occur ex-nihilo. After searching the forums, and the wiki, if you cannot find the documentation you require, try creating it. Start a page on the wiki, and post in the forums regarding it. Likely other people have experience in the area, or are at least willing to help.<br />
If nobody does, don't be discouraged. When you finish your documentation, other people will likely find it an extremely valuable resource.<br />
There is always a need for documentation, contribute to the wiki.<br />
<br />
==Q) Arch needs more devs==<br />
'''A)''' Possibly so. Feel free to volunteer your time! Visit the forums, irc channel, mailing lists, and see what needs to be done.<br />
There is always a need for documentation, contribute to this wiki.<br />
<br />
==Q) Why is Arch so slow? I thought it's supposed to be fast!==<br />
'''A)''' There are two common reasons that your system may be slower than it should. First, ensure that loopback (lo in /etc/rc.conf) is enabled. Second, make sure that your hostname is correctly set in /etc/hosts. Either reason can cause applications to startup very slow, for example.<br />
<br />
=Package Management=<br />
<br />
==Q) I've found an error with package X, what should I do?==<br />
'''A)''' First you need to figure out if this error is something the Arch team can fix. Sometimes it's not (that firefox crash may be the fault of the Mozilla team) - this is called an ''upstream error''. If it is an Arch problem, there are a series of steps you can take:<br />
#Search the forums for information. See if anyone else has noticed it.<br />
#Notify the package maintainer. Try a "pacman -Qi <package name>" for this info.<br />
#Post a bug report, with detailed information at http://bugs.archlinux.org<br />
#Write a forum post if you'd like, detailing the problem and the fact that you have reported it already. This will help prevent a lot of people from reporting the same error.<br />
<br />
<br />
==Q) Will Arch have a database for pacman?==<br />
'''A)''' Possibly. There is discussion over the issue.<br />
http://bbs.archlinux.org/viewtopic.php?t=11193<br />
http://bbs.archlinux.org/viewtopic.php?t=10898<br />
Look at http://bugs.archlinux.org/task/5328 too.<br />
<br />
<br />
==Q) Pacman is slow! How can initial start times be improved?==<br />
'''A)''' See previous entry relating to a database back end for pacman. Only the first pacman run after a boot should be slow. After that, things are generally cached. Still, initial start time is an issue for some people. There is discussion on addressing this.<br />
If you are on [[ReiserFS]], there are issues with fragmentation that slow down pacman more than necessary. <br />
Since version 2.9.6, the pacman package bundles a bash script called <tt>pacman-optimize</tt> that should help anyone experiencing slow start-up times. Also see:[[Improve Pacman Performance]]<br />
<br />
<br />
==Q) Arch packages need to use a unique naming convention. .pkg.tar.gz is too long, and or, confusing==<br />
'''A)''' This has been discussed on the Arch mailing list. Some proposed a .pac file extension. As far as is currently known, there is no plan to change the package extension.<br />
As Tobias Kieslich, one of the Arch devs, put it, "A package '''is''' a gzipped tarball! And it can be opened, investigated and manipulated by any tar capable application. Moreover, the mime-type is automatically detected correctly by most applications."<br />
<br />
<br />
==Q) Pacman needs a library so other applications can easily access package information==<br />
'''A)''' A library for pacman is in progress. That does not imply a release date.<br />
<br />
<br />
==Q) Why doesn't Pacman have a GUI front-end?==<br />
'''A)''' Did you read [[The Arch Way]] and [[ArchLinux]] and [[Devland]]?<br />
The answer is basically that the Arch dev team will not be providing one. Feel free to use one those developed by users. There is a nice list of them on the [[UserContributionsPage]] in the links section, and a selective list on [[Pacman_GUI_Frontends]]. Once the library for pacman is done, it will be much easier for the various frontends to interact with Arch packages.<br />
<br />
<br />
==Q) Pacman needs feature X!==<br />
'''A)''' Did you read [[TheArchWay]] and [[ArchLinux]] and [[Devland]]?<br />
The Arch philosophy is "Keep It Simple". If you think the idea has merit, and does not violate this simple litany, then by all means, discuss it on the forum [http://bbs.archlinux.org/ here]<br />
You might also like to check [http://bugs.archlinux.org here], it's a place for feature requests if you find it is important.<br />
<br />
However, the best way to get a feature added to Pacman or Arch Linux is to implement it yourself. There's no telling whether the patch will be officially accepted, but others will appreciate and test your effort.<br />
<br />
<br />
==Q) Arch needs a stable package branch==<br />
'''A)'''<br />
COMMENT: "For me, In short, Arch is Rock-solid enough."<br />
<br />
REPLY: It depends on what type of work we use our machine for. For example, in office work we don't want our printer to stop working. In multimedia work our cd burner must function. Web developers need functional ftp clients. Currently I am annoyed with kde-3.4 because I lost all my bookmarks in kbear (ftp). New bookmarks cannot be saved.<br />
<br />
SOLUTION: There is a '''release''' '''repo''' which is stable, though not supporting all packages. There are thoughts of including all major packages (kde, gnome, etc). <br><br />
ftp://ftp.archlinux.org/release/os/i686/<br />
<br />
Read more: <br><br />
http://bbs.archlinux.org/viewtopic.php?t=11288<br />
<br />
<br />
==Q) What's the difference between all these repositories?==<br />
'''A)''' See [[The Arch Linux Repositories]]<br />
<br />
<br />
==Q) Why doesn't Arch include docs and info pages in its packages?==<br />
'''A)''' In it's goal to be simple and lightweight, the relatively useless portions of a linux system have been left out, things like /usr/doc and the info pages, in favor of man pages. This question is brought up a lot, read some past discussions about it:<br />
http://www.archlinux.org/pipermail/arch/2005-April/004194.html<br />
http://bbs.archlinux.org/viewtopic.php?id=14527<br />
<br />
<br />
==Q) I just installed Package X. How do I start it?==<br />
'''A)''' If you're using a desktop environment like KDE or GNOME, the program should automatically show up in your menu. If you're trying to run the program from a terminal and don't know the binary name, try executing "pacman -Ql packagename | grep bin". A common problem for packages like Firefox or OpenOffice is that they are installed to /opt, which is not in your $PATH - you can "source /etc/profile" or logout/login to fix this.<br />
<br />
<br />
=Installation=<br />
<br />
==Q) Arch needs a better installer. Maybe a GUI installer.==<br />
'''A)''' The discussion of a "better" installer is a subjective opinion. The best way to cope with these issues it to fit the installer<br />
to "the arch way". If this opinion on a better installer is backed with more concrete arguments, it might be taken into account for further development of the installer. Since installation doesn't occur often (see the question above on rolling release), it is not a high priority for developers or users.</div>Neotulihttps://wiki.archlinux.org/index.php?title=Frequently_asked_questions&diff=21974Frequently asked questions2007-03-16T22:05:56Z<p>Neotuli: Reverted edits by Neotuli (Talk); changed back to last version by Ngch</p>
<hr />
<div>[[Category:About Arch (English)]]<br />
[[Category:FAQs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|FAQ}}<br />
{{i18n_entry|Español|FAQ_(Español)}}<br />
{{i18n_entry|Nederlands|FAQ_(Nederlands)}}<br />
{{i18n_entry|Français|FAQ (Français)}}<br />
{{i18n_entry|Polski|FAQ (Polski)}}<br />
{{i18n_entry|简体中文|FAQ常见问题集}}<br />
{{i18n_entry|Slovensky|FAQ_(Slovensky)}}<br />
{{i18n_entry|Česky|FAQ_(Česky)}}<br />
{{i18n_entry|Deutsch|FAQ_(Deutsch)}}<br />
{{i18n_entry|Português do Brasil|FAQ_(Português do Brasil)}}<br />
{{i18n_entry|Русский|FAQ_(Русский)}}<br />
{{i18n_entry|ไทย|FAQ_(ไทย)}}<br />
{{i18n_links_end}}<br />
<br />
Besides the questions covered below, you may find [[The Arch Way]],[[ArchLinux]], and [[Devland]] helpful. All three contain a good deal of information about ArchLinux.<br />
<br />
= General =<br />
<br />
==Q) I am a complete Linux beginner. Should I use Arch?==<br />
'''A)''' This question has had much debate. Arch is targeted at more advanced Linux users, but some people feel "Arch is a good place to start". If you are a beginner and wants to use Arch, just be warned that you MUST be willing to learn. Before asking any question, do your own independent research by googling, searching the Wiki, and searching the forum (and reading past FAQs). If you do that, you should be fine. Also know that many people do not want to answer the same basic questions over and over, so you are exposing yourself to that environment. There is a reason these resources were created/made available to you. You could reference the [[ArchLinux Newbie Guide]]<br />
<br />
==Q) When will the new release be made?==<br />
'''A)''' Arch Linux releases are quite infrequent, and usually only happen when a major change has been made to the installer or something has happened that makes it difficult to run ''pacman -Syu'' to update from the previous release.<br />
<br />
Releases are not terribly important in Arch, because the so-called 'rolling release' system makes new releases out of date as soon as a package has been updated. If you are looking to obtain the latest Arch Linux release, you do not need to reinstall. You simply run the ''pacman -Syu'' command and your system will be identical to what you would get with a brand new install.<br />
<br />
For this same reason, new Arch Linux releases are not typically full of new and exciting features. New and exciting features are released as needed with the packages that are updated, and can be obtained immediately via ''pacman -Syu''<br />
<br />
<br />
==Q) Arch needs more/less press (ie advertisement)==<br />
'''A)''' Arch gets plenty of press as it is. The goal of ArchLinux is not to be large. The goal is to be well done. Let growth occur naturally. Trying to force it to grow too quickly will just cause problems.<br />
<br />
Similarly, do not try to restrict the natural growth. More users might mean more devs to work on ArchLinux. This may cause some organizational issues at the "top", but those will be dealt with when they arrive.<br />
<br />
==Q) Arch needs more documentation==<br />
'''A)'''This is essentially true, so feel free to contribute. Documentation does not occur ex-nihilo. After searching the forums, and the wiki, if you cannot find the documentation you require, try creating it. Start a page on the wiki, and post in the forums regarding it. Likely other people have experience in the area, or are at least willing to help.<br />
If nobody does, don't be discouraged. When you finish your documentation, other people will likely find it an extremely valuable resource.<br />
There is always a need for documentation, contribute to the wiki.<br />
<br />
==Q) Arch needs more devs==<br />
'''A)''' Possibly so. Feel free to volunteer your time! Visit the forums, irc channel, mailing lists, and see what needs to be done.<br />
There is always a need for documentation, contribute to this wiki.<br />
<br />
==Q) Why is Arch so slow? I thought it's supposed to be fast!==<br />
'''A)''' There are two common reasons that your system may be slower than it should. First, ensure that loopback (lo in /etc/rc.conf) is enabled. Second, make sure that your hostname is correctly set in /etc/hosts. Either reason can cause applications to startup very slow, for example.<br />
<br />
=Package Management=<br />
<br />
==Q) I've found an error with package X, what should I do?==<br />
'''A)''' First you need to figure out if this error is something the Arch team can fix. Sometimes it's not (that firefox crash may be the fault of the Mozilla team) - this is called an ''upstream error''. If it is an Arch problem, there are a series of steps you can take:<br />
#Search the forums for information. See if anyone else has noticed it.<br />
#Notify the package maintainer. Try a "pacman -Qi <package name>" for this info.<br />
#Post a bug report, with detailed information at http://bugs.archlinux.org<br />
#Write a forum post if you'd like, detailing the problem and the fact that you have reported it already. This will help prevent a lot of people from reporting the same error.<br />
<br />
<br />
==Q) Will Arch have a database for pacman?==<br />
'''A)''' Possibly. There is discussion over the issue.<br />
http://bbs.archlinux.org/viewtopic.php?t=11193<br />
http://bbs.archlinux.org/viewtopic.php?t=10898<br />
Look at http://bugs.archlinux.org/task/5328 too.<br />
<br />
<br />
==Q) Pacman is slow! How can initial start times be improved?==<br />
'''A)''' See previous entry relating to a database back end for pacman. Only the first pacman run after a boot should be slow. After that, things are generally cached. Still, initial start time is an issue for some people. There is discussion on addressing this.<br />
If you are on [[ReiserFS]], there are issues with fragmentation that slow down pacman more than necessary. <br />
Since version 2.9.6, the pacman package bundles a bash script called <tt>pacman-optimize</tt> that should help anyone experiencing slow start-up times. Also see:[[Improve Pacman Performance]]<br />
<br />
<br />
==Q) Arch packages need to use a unique naming convention. .pkg.tar.gz is too long, and or, confusing==<br />
'''A)''' This has been discussed on the Arch mailing list. Some proposed a .pac file extension. As far as is currently known, there is no plan to change the package extension.<br />
As Tobias Kieslich, one of the Arch devs, put it, "A package '''is''' a gzipped tarball! And it can be opened, investigated and manipulated by any tar capable application. Moreover, the mime-type is automatically detected correctly by most applications."<br />
<br />
<br />
==Q) Pacman needs a library so other applications can easily access package information==<br />
'''A)''' A library for pacman is in progress. That does not imply a release date.<br />
<br />
<br />
==Q) Why doesn't Pacman have a GUI front-end?==<br />
'''A)''' Did you read [[The Arch Way]] and [[ArchLinux]] and [[Devland]]?<br />
The answer is basically that the Arch dev team will not be providing one. Feel free to use one those developed by users. There is a nice list of them on the [[UserContributionsPage]] in the links section, and a selective list on [[Pacman_GUI_Frontends]]. Once the library for pacman is done, it will be much easier for the various frontends to interact with Arch packages.<br />
<br />
<br />
==Q) Pacman needs feature X!==<br />
'''A)''' Did you read [[TheArchWay]] and [[ArchLinux]] and [[Devland]]?<br />
The Arch philosophy is "Keep It Simple". If you think the idea has merit, and does not violate this simple litany, then by all means, discuss it on the forum [http://bbs.archlinux.org/ here]<br />
You might also like to check [http://bugs.archlinux.org here], it's a place for feature requests if you find it is important.<br />
<br />
However, the best way to get a feature added to Pacman or Arch Linux is to implement it yourself. There's no telling whether the patch will be officially accepted, but others will appreciate and test your effort.<br />
<br />
<br />
==Q) Arch needs a stable package branch==<br />
'''A)'''<br />
COMMENT: "For me, In short, Arch is Rock-solid enough."<br />
<br />
REPLY: It depends on what type of work we use our machine for. For example, in office work we don't want our printer to stop working. In multimedia work our cd burner must function. Web developers need functional ftp clients. Currently I am annoyed with kde-3.4 because I lost all my bookmarks in kbear (ftp). New bookmarks cannot be saved.<br />
<br />
SOLUTION: There is a '''release''' '''repo''' which is stable, though not supporting all packages. There are thoughts of including all major packages (kde, gnome, etc). <br><br />
ftp://ftp.archlinux.org/release/os/i686/<br />
<br />
Read more: <br><br />
http://bbs.archlinux.org/viewtopic.php?t=11288<br />
<br />
<br />
==Q) What's the difference between all these repositories?==<br />
'''A)''' See [[The Arch Linux Repositories]]<br />
<br />
<br />
==Q) Why doesn't Arch include docs and info pages in its packages?==<br />
'''A)''' In it's goal to be simple and lightweight, the relatively useless portions of a linux system have been left out, things like /usr/doc and the info pages, in favor of man pages. This question is brought up a lot, read some past discussions about it:<br />
http://www.archlinux.org/pipermail/arch/2005-April/004194.html<br />
http://bbs.archlinux.org/viewtopic.php?id=14527<br />
<br />
<br />
==Q) I just installed Package X. How do I start it?==<br />
'''A)''' If you're using a desktop environment like KDE or GNOME, the program should automatically show up in your menu. If you're trying to run the program from a terminal and don't know the binary name, try executing "pacman -Ql packagename | grep bin". A common problem for packages like Firefox or OpenOffice is that they are installed to /opt, which is not in your $PATH - you can "source /etc/profile" or logout/login to fix this.<br />
<br />
<br />
=Installation=<br />
<br />
==Q) Arch needs a better installer. Maybe a GUI installer.==<br />
'''A)''' The discussion of a "better" installer is a subjective opinion. The best way to cope with these issues it to fit the installer<br />
to "the arch way". If this opinion on a better installer is backed with more concrete arguments, it might be taken into account for further development of the installer. Since installation doesn't occur often (see the question above on rolling release), it is not a high priority for developers or users.</div>Neotulihttps://wiki.archlinux.org/index.php?title=Frequently_asked_questions&diff=21973Frequently asked questions2007-03-16T22:05:46Z<p>Neotuli: gammar fix</p>
<hr />
<div>[[Category:About Arch (English)]]<br />
[[Category:FAQs (English)]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|FAQ}}<br />
{{i18n_entry|Español|FAQ_(Español)}}<br />
{{i18n_entry|Nederlands|FAQ_(Nederlands)}}<br />
{{i18n_entry|Français|FAQ (Français)}}<br />
{{i18n_entry|Polski|FAQ (Polski)}}<br />
{{i18n_entry|简体中文|FAQ常见问题集}}<br />
{{i18n_entry|Slovensky|FAQ_(Slovensky)}}<br />
{{i18n_entry|Česky|FAQ_(Česky)}}<br />
{{i18n_entry|Deutsch|FAQ_(Deutsch)}}<br />
{{i18n_entry|Português do Brasil|FAQ_(Português do Brasil)}}<br />
{{i18n_entry|Русский|FAQ_(Русский)}}<br />
{{i18n_entry|ไทย|FAQ_(ไทย)}}<br />
{{i18n_links_end}}<br />
<br />
Besides the questions covered below, you may find [[The Arch Way]],[[ArchLinux]], and [[Devland]] helpful. All three contain a good deal of information about ArchLinux.<br />
<br />
= General =<br />
<br />
==Q) I am a complete Linux beginner. Should I use Arch?==<br />
'''A)''' This question has had much debate. Arch is targeted at more advanced Linux users, but some people feel "Arch is a good place to start". If you are a beginner and want to use Arch, just be warned that you MUST be willing to learn. Before asking any question, do your own independent research by googling, searching the Wiki, and searching the forum (and reading past FAQs). If you do that, you should be fine. Also know that many people do not want to answer the same basic questions over and over, so you are exposing yourself to that environment. There is a reason these resources were created/made available to you. You could reference the [[ArchLinux Newbie Guide]]<br />
<br />
==Q) When will the new release be made?==<br />
'''A)''' Arch Linux releases are quite infrequent, and usually only happen when a major change has been made to the installer or something has happened that makes it difficult to run ''pacman -Syu'' to update from the previous release.<br />
<br />
Releases are not terribly important in Arch, because the so-called 'rolling release' system makes new releases out of date as soon as a package has been updated. If you are looking to obtain the latest Arch Linux release, you do not need to reinstall. You simply run the ''pacman -Syu'' command and your system will be identical to what you would get with a brand new install.<br />
<br />
For this same reason, new Arch Linux releases are not typically full of new and exciting features. New and exciting features are released as needed with the packages that are updated, and can be obtained immediately via ''pacman -Syu''<br />
<br />
<br />
==Q) Arch needs more/less press (ie advertisement)==<br />
'''A)''' Arch gets plenty of press as it is. The goal of ArchLinux is not to be large. The goal is to be well done. Let growth occur naturally. Trying to force it to grow too quickly will just cause problems.<br />
<br />
Similarly, do not try to restrict the natural growth. More users might mean more devs to work on ArchLinux. This may cause some organizational issues at the "top", but those will be dealt with when they arrive.<br />
<br />
==Q) Arch needs more documentation==<br />
'''A)'''This is essentially true, so feel free to contribute. Documentation does not occur ex-nihilo. After searching the forums, and the wiki, if you cannot find the documentation you require, try creating it. Start a page on the wiki, and post in the forums regarding it. Likely other people have experience in the area, or are at least willing to help.<br />
If nobody does, don't be discouraged. When you finish your documentation, other people will likely find it an extremely valuable resource.<br />
There is always a need for documentation, contribute to the wiki.<br />
<br />
==Q) Arch needs more devs==<br />
'''A)''' Possibly so. Feel free to volunteer your time! Visit the forums, irc channel, mailing lists, and see what needs to be done.<br />
There is always a need for documentation, contribute to this wiki.<br />
<br />
==Q) Why is Arch so slow? I thought it's supposed to be fast!==<br />
'''A)''' There are two common reasons that your system may be slower than it should. First, ensure that loopback (lo in /etc/rc.conf) is enabled. Second, make sure that your hostname is correctly set in /etc/hosts. Either reason can cause applications to startup very slow, for example.<br />
<br />
=Package Management=<br />
<br />
==Q) I've found an error with package X, what should I do?==<br />
'''A)''' First you need to figure out if this error is something the Arch team can fix. Sometimes it's not (that firefox crash may be the fault of the Mozilla team) - this is called an ''upstream error''. If it is an Arch problem, there are a series of steps you can take:<br />
#Search the forums for information. See if anyone else has noticed it.<br />
#Notify the package maintainer. Try a "pacman -Qi <package name>" for this info.<br />
#Post a bug report, with detailed information at http://bugs.archlinux.org<br />
#Write a forum post if you'd like, detailing the problem and the fact that you have reported it already. This will help prevent a lot of people from reporting the same error.<br />
<br />
<br />
==Q) Will Arch have a database for pacman?==<br />
'''A)''' Possibly. There is discussion over the issue.<br />
http://bbs.archlinux.org/viewtopic.php?t=11193<br />
http://bbs.archlinux.org/viewtopic.php?t=10898<br />
Look at http://bugs.archlinux.org/task/5328 too.<br />
<br />
<br />
==Q) Pacman is slow! How can initial start times be improved?==<br />
'''A)''' See previous entry relating to a database back end for pacman. Only the first pacman run after a boot should be slow. After that, things are generally cached. Still, initial start time is an issue for some people. There is discussion on addressing this.<br />
If you are on [[ReiserFS]], there are issues with fragmentation that slow down pacman more than necessary. <br />
Since version 2.9.6, the pacman package bundles a bash script called <tt>pacman-optimize</tt> that should help anyone experiencing slow start-up times. Also see:[[Improve Pacman Performance]]<br />
<br />
<br />
==Q) Arch packages need to use a unique naming convention. .pkg.tar.gz is too long, and or, confusing==<br />
'''A)''' This has been discussed on the Arch mailing list. Some proposed a .pac file extension. As far as is currently known, there is no plan to change the package extension.<br />
As Tobias Kieslich, one of the Arch devs, put it, "A package '''is''' a gzipped tarball! And it can be opened, investigated and manipulated by any tar capable application. Moreover, the mime-type is automatically detected correctly by most applications."<br />
<br />
<br />
==Q) Pacman needs a library so other applications can easily access package information==<br />
'''A)''' A library for pacman is in progress. That does not imply a release date.<br />
<br />
<br />
==Q) Why doesn't Pacman have a GUI front-end?==<br />
'''A)''' Did you read [[The Arch Way]] and [[ArchLinux]] and [[Devland]]?<br />
The answer is basically that the Arch dev team will not be providing one. Feel free to use one those developed by users. There is a nice list of them on the [[UserContributionsPage]] in the links section, and a selective list on [[Pacman_GUI_Frontends]]. Once the library for pacman is done, it will be much easier for the various frontends to interact with Arch packages.<br />
<br />
<br />
==Q) Pacman needs feature X!==<br />
'''A)''' Did you read [[TheArchWay]] and [[ArchLinux]] and [[Devland]]?<br />
The Arch philosophy is "Keep It Simple". If you think the idea has merit, and does not violate this simple litany, then by all means, discuss it on the forum [http://bbs.archlinux.org/ here]<br />
You might also like to check [http://bugs.archlinux.org here], it's a place for feature requests if you find it is important.<br />
<br />
However, the best way to get a feature added to Pacman or Arch Linux is to implement it yourself. There's no telling whether the patch will be officially accepted, but others will appreciate and test your effort.<br />
<br />
<br />
==Q) Arch needs a stable package branch==<br />
'''A)'''<br />
COMMENT: "For me, In short, Arch is Rock-solid enough."<br />
<br />
REPLY: It depends on what type of work we use our machine for. For example, in office work we don't want our printer to stop working. In multimedia work our cd burner must function. Web developers need functional ftp clients. Currently I am annoyed with kde-3.4 because I lost all my bookmarks in kbear (ftp). New bookmarks cannot be saved.<br />
<br />
SOLUTION: There is a '''release''' '''repo''' which is stable, though not supporting all packages. There are thoughts of including all major packages (kde, gnome, etc). <br><br />
ftp://ftp.archlinux.org/release/os/i686/<br />
<br />
Read more: <br><br />
http://bbs.archlinux.org/viewtopic.php?t=11288<br />
<br />
<br />
==Q) What's the difference between all these repositories?==<br />
'''A)''' See [[The Arch Linux Repositories]]<br />
<br />
<br />
==Q) Why doesn't Arch include docs and info pages in its packages?==<br />
'''A)''' In it's goal to be simple and lightweight, the relatively useless portions of a linux system have been left out, things like /usr/doc and the info pages, in favor of man pages. This question is brought up a lot, read some past discussions about it:<br />
http://www.archlinux.org/pipermail/arch/2005-April/004194.html<br />
http://bbs.archlinux.org/viewtopic.php?id=14527<br />
<br />
<br />
==Q) I just installed Package X. How do I start it?==<br />
'''A)''' If you're using a desktop environment like KDE or GNOME, the program should automatically show up in your menu. If you're trying to run the program from a terminal and don't know the binary name, try executing "pacman -Ql packagename | grep bin". A common problem for packages like Firefox or OpenOffice is that they are installed to /opt, which is not in your $PATH - you can "source /etc/profile" or logout/login to fix this.<br />
<br />
<br />
=Installation=<br />
<br />
==Q) Arch needs a better installer. Maybe a GUI installer.==<br />
'''A)''' The discussion of a "better" installer is a subjective opinion. The best way to cope with these issues it to fit the installer<br />
to "the arch way". If this opinion on a better installer is backed with more concrete arguments, it might be taken into account for further development of the installer. Since installation doesn't occur often (see the question above on rolling release), it is not a high priority for developers or users.</div>Neotulihttps://wiki.archlinux.org/index.php?title=Main_page&diff=21863Main page2007-03-11T02:17:49Z<p>Neotuli: </p>
<hr />
<div>__NOTOC__ __NOEDITSECTION__<br />
{{Navigate_i18n_mainpages}}<br />
Welcome to the [[ArchLinux]] Wiki. If you are new to Arch, you may be interested in the [[Beginners Guide]]. Otherwise, dig right in.<br />
<br />
==== &nbsp;&nbsp;[[:Category: About Arch (English)|About Arch]] ====<br />
: [[The Arch Way]] :: [[Arch vs Others]] :: [[FAQ]] :: [[Official Repositories]] :: [[ArchLinux User-community Repository (AUR)|Arch User Repository (AUR)]]<br />
<br />
==== &nbsp;&nbsp;[[:Category: Getting and installing Arch (English)|Getting and Installing Arch]] ====<br />
: [[Official Arch Linux Install Guide|Official Install Guide]] :: [[Post Installation Tips]] :: [[Configuring network|Configuring Network]]<br />
<br />
==== &nbsp;&nbsp;[[:Category: System administration (English)|System Administration]] ====<br />
: [[Pacman]] :: [[:Category: Package management (English)|Package Management]] :: [[Xorg7|Xorg Setup]] :: [[:Category: Desktop environments (English)|Desktop Environments]] :: [[ALSA Setup]]<br />
<br />
==== &nbsp;&nbsp;[[:Category: Desktop user's guide (English)|Desktop User's Guide]] ====<br />
: [[:Category: Internet and Email (English)|Internet and Email]] :: [[:Category: Office (English)|Office]] :: [[:Category: Audio/Video (English)|Audio/Video]]<br />
<br />
==== &nbsp;&nbsp;[[:Category:System recovery (English)|System Recovery]] ====<br />
: [[Reinstalling GRUB]] :: [[Kernel Panics]]<br />
<br />
==== &nbsp;&nbsp;[[:Category: Arch Development (English)|Arch Development]] ====<br />
<br />
==== &nbsp;&nbsp;[[:Category:Arch64 (English)|Arch64]] ====<br />
: [[Arch64 FAQ]]<br />
<br />
==== &nbsp;&nbsp;[[:Category: Live Arch systems (English)|Live Arch Systems]] ====<br />
:: &nbsp;<br />
<br />
== Wiki News ==<br />
<br />
Check the [[Wiki News]] page for the latest lowdown on the Wiki.<br />
<br />
Note that we are currently in the process of editing the wiki structure. If you have some time to make minor or major edits, take a look at the [[Priority Todo]] and the [[WikiTodo]] pages to see how you can help. We're especially interested in having people recategorize the non-English pages. Please coordinate your activities with [[ContactList|admins and sysops]] or [[ArchWiki maintainers (English)|maintainers]].<br />
<br />
== In Your Language ==<br />
More comfortable reading articles in your own language? Browse the categories for the following languages: <br />
: [[:Category:English|English]] :: [[:Category:Česky|Česky]] :: [[:Category:Deutsch|Deutsch]] :: [[:Category:Français|Français]] :: [[:Category:Italiano|Italiano]] :: [[:Category:Polski|Polski]] :: [[:Category:Русский|Русский]] :: [[:Category:Српски|Српски]] :: [[:Category:ไทย|ไทย]]<br />
<br />
== Help ==<br />
If you're having trouble finding what you're looking for, try using the search box to the left.<br />
<br />
You must create an account to edit this wiki. Once done, you can play around in the [[Sandbox]] or your user page to familiarize yourself with ArchWiki markup. The available syntax is listed in the [[:Category:Help|Wiki Help Category]] and there is an [[:Category:ArchWiki Tools (English)|Archwiki Tools section]] with some HOWTOs and guidelines.</div>Neotulihttps://wiki.archlinux.org/index.php?title=Template:META_Message&diff=21554Template:META Message2007-03-04T05:04:54Z<p>Neotuli: Protected "Template:Message box" [edit=sysop:move=sysop]</p>
<hr />
<div><center><div style="text-align: center; margin: 0 10% 1em 10%;"><br />
{| class="notice noprint" id="{{{id}}}" style="background: {{{backgroundcolor}}}; border: 1px solid #aaa; padding: 0.1em; margin: 0.5em auto;"<br />
|-<br />
| valign="top" style="padding: 0.1em; background-color: {{{signalcolor}}}" | {{{signal}}}<br />
| style="padding: 0.1em" | '''{{{heading}}}'''<br><div style="font-size: 90%;">{{{message}}}</div><br />
|}<br />
</div></center></div>Neotulihttps://wiki.archlinux.org/index.php?title=Arch_Linux_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=21521Arch Linux (简体中文)2007-03-03T17:56:01Z<p>Neotuli: </p>
<hr />
<div>[[Category:简体中文]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|Deutsch|ArchLinux (Deutsch)}}<br />
{{i18n_entry|English|ArchLinux}}<br />
{{i18n_entry|Finnish|ArchLinux (Suomi)}}<br />
{{i18n_entry|Français|ArchLinux (Français)}}<br />
{{i18n_entry|Polski|ArchLinux (Polski)}}<br />
{{i18n_entry|Português do Brasil|ArchLinux_(Portugues_do_Brasil)}}<br />
{{i18n_entry|繁體中文|ArchLinux (繁體中文)}}<br />
{{i18n_entry|简体中文|ArchLinux (简体中文)}}<br />
{{i18n_entry|Русский|ArchLinux (Русский)}}<br />
{{i18n_entry|Slovensky|ArchLinux_(Slovensky)}}<br />
{{i18n_entry|עברית|ArchLinux (עברית)}}<br />
{{i18n_links_end}}<br />
= Arch Linux 是什么? =<br />
<br />
Arch Linux 是个 '''针对 i686 优化的 linux 发行版'''。最初灵感源于 Per Lidén 开发的一个非常不错的 CRUX 发行版。<br />
<br />
== 优势 ==<br />
Arch 基本理念是快速、轻巧、弹性与简单。这并非华而不实的行话,他们都是事实。Arch 是为 i686 处理器优化的, 所以可以为你取得更多的cpu cycle(快速)。他相较于 RedHat 或是其他的 Linux 而言是轻巧的, 而且简单的设计使他富有弹性并且可以成为任何你想建立的系统的模型。<br />
<br />
== 特有的包管理 ==<br />
通过可以轻松使用的二进制包系统 - [[pacman]] - 一个命令就让您升级整个系统。Arch 同时也拥有一个类似 ports 的包构建系统(Arch Build System),通过它可以轻松构建软件包。它也是一个命令就可完成同步。哦,是的,您也可以用一个命令重新构建(rebuild)整个系统。所有事情都是在一个非常简单、明了的情况下完成的。<br />
<br />
== 只要最好的 ==<br />
Arch Linux 的使用者和发展者也很有效率的支持维护 current 与 extra 集,让Arch Linux的软件维持在最新的稳定版。<br />
<br />
== 简单是关键 ==<br />
Arch 要达到的目标是简单和轻巧,我已经省去于 linux 系统无用的相关部分,比如 /usr/doc 和 info pages。按我个人经验,这些都是没多大用处的,而且真的需要时,可以从网络上获取等价的信息。Man panges 就足够了...<br />
<br />
== 时髦的工具 ==<br />
Arch Linux 努力采用用户可以使用的更新的特性,比如 Ext3/ReiserFS 和 udev 等。Arch Linux 0.7 (Wombat) 缺省使用 2.6 的 linux 内核,而且支持 XFS/JFS。<br />
<br />
== 进一步了解 ==<br />
Arch 的主页在 http://www.archlinux.org/ ,在那里您可以找到 [http://bbs.archlinux.org 用户论坛]的链接,官方文档,和所有其他 Arch 相关的东西。也可以通过阅读 [[TheArchWay]]</div>Neotulihttps://wiki.archlinux.org/index.php?title=Arch_Linux_(Portugu%C3%AAs)&diff=21520Arch Linux (Português)2007-03-03T17:55:17Z<p>Neotuli: added language category</p>
<hr />
<div>[[Category:Português do Brasil]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|Deutsch|ArchLinux (Deutsch)}}<br />
{{i18n_entry|English|ArchLinux}}<br />
{{i18n_entry|Finnish|ArchLinux (Suomi)}}<br />
{{i18n_entry|Français|ArchLinux (Français)}}<br />
{{i18n_entry|Polski|ArchLinux (Polski)}}<br />
{{i18n_entry|Português do Brasil|ArchLinux_(Português_do_Brasil)}}<br />
{{i18n_entry|繁體中文|ArchLinux (繁體中文)}}<br />
{{i18n_entry|简体中文|ArchLinux (简体中文)}}<br />
{{i18n_entry|Русский|ArchLinux (Русский)}}<br />
{{i18n_entry|Slovensky|ArchLinux_(Slovensky)}}<br />
{{i18n_entry|עברית|ArchLinux (עברית)}}<br />
{{i18n_links_end}}<br />
<br />
<br />
= O que é Arch Linux? =<br />
<br />
Arch Linux é uma '''distribuição linux otimizada para i686''', baseada originalmente em idéias oriundas da CRUX, uma notável distribuição desenvolvida por Per Lidén.<br />
<br />
== Vantagens ==<br />
Arch é rápida, leve, flexível e simples. Estas não são apenas palavras de impacto, mas a pura verdade. Arch é otimizada para processadores i686; assim, você aproveita melhor seus ciclos de cpu. Ela é leve, se comparada à RedHat e outras, e o seu projeto simples faz com que suas funcionalidades sejam facilmente estendidas e moldadas a qualquer tipo de sistema que você queira construir.<br />
<br />
== Gerenciamento de pacotes único ==<br />
Tem como fundamento um sistema de pacotes binários fácil de usar - [[pacman]] - permitindo que se atualize todo o sistema com apenas um único comando. A Arch utiliza ainda um sistema de construção de pacotes do tipo ''ports'' (Arch Build System [Sistema de Construção Arch]) a fim de facilitar a construção de pacotes pelo usuário, sistema que também pode ser sincronizado com um único comando. Tudo é feito de forma simples e transparente.<br />
<br />
== Apenas o melhor ==<br />
A Arch Linux se empenha em manter os seus programas na sua versão estável mais recente. No momento suportamos um conjunto de pacotes principais bastante atualizada com uma crescente coleção de pacotes extras criados por usuários e desenvolvedores do AL.<br />
<br />
== Simplicidade é a chave ==<br />
A fim de assegurar a sua simplicidade e leveza, foram retiradas do sistema partes de uso relativamente escasso no Linux, tais como /usr/doc e paginas ''info''. Segundo minha própria experiência, muito raramente se recorre a elas, e informação equivalente pode ser obtida na Internet, se necessário. Páginas ''man'' estão em toda parte...<br />
<br />
== Ferramentas modernas ==<br />
A Arch Linux também se esforça por usar algumas das mais novas características disponíveis para os usuários Linux, como suporte a Ext3/ReiserFS e udev. A Arch Linux 0.7 (Wombat) usa kernel linux 2.6 por padrão, e tem suporte a XFS/JFS.<br />
<br />
== Literatura adicional ==<br />
A homepage da Arch está em http://www.archlinux.org/, onde se pode encontrar links para o fórum de usuários, documentação oficial, e tudo o mais que é o Arch. Você pode também ler o [[TheArchWay]] para compreender um pouco mais do jeito do Arch.</div>Neotulihttps://wiki.archlinux.org/index.php?title=Arch_User_Repository_(Portugu%C3%AAs)&diff=21518Arch User Repository (Português)2007-03-03T17:53:18Z<p>Neotuli: added language category</p>
<hr />
<div>[[Category:Português do Brasil]]<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|AUR_Q_%26_A}}<br />
{{i18n_entry|Português do Brasil|AUR - Perguntas e respostas}}<br />
{{i18n_links_end}}<br />
<br />
=Questões Comuns=<br />
==O que é o AUR ?==<br />
AUR (Arch User Repository - Repositório do Usuário Arch) é um local para onde a comunidade Archlinux pode enviar <br />
PKGBUILDs de aplicações, bibliotecas, etc e compartilhá-los entre todos os seus membros. Outros usuários podem votar pelos seus favoritos para que entrem para o repositório Community (Comunidade), para serem compartilhados entre os usuários Archlinux em formato binário.<br />
<br />
==O que é um TU?==<br />
Um TU (Trusted User - Usuário de Confiança) é uma pessoa que é escolhida para zelar pelos repositórios AUR e Community (Comunidade). Eles são os que colocam os PKGBUILDs mais votados no repositório Community (Comunidade), marcam PKGBUILDs como seguros e sobretudo mantém o AUR funcionando.<br />
Qual a diferença entre Unsupported (Não suportado) e Community (Comunidade)?<br />
Unsupported (Não suportado) é onde ficam todos os PKGBUILDs que os usuários enviam, eles devem ser montados manualmente com makepkg.<br />
Os PKGBUILDs que obtém votos suficientes vão para o repositório Community (Comunidade), onde os TUs os mantém e de onde podem ser instalados através do pacman, uma vez que eles agora são pacotes binários.<br />
<br />
Quantos votos são necessários para levar um PKGBUILD para o Community (Comunidade)?<br />
Normalmente são precisos 25 votos para algo ir para o Community (Comunidade). Uma exceção a isso é se uma aplicação é desenvolvida no Archlinux e um TU deseja colocá-lo diretamente nesse repositório.<br />
<br />
==Onde eu obtenho informação sobre como criar um PKGBUILD?==<br />
O melhor local para se obter essa informação é nesta entrada do wiki. Lembre-se de verificar o AUR antes de criar o PKGBUILD de maneira a não duplicar esforços.<br />
<br />
=Problemas Comuns=<br />
Eu tento usar pacman -S foo e não funciona, mas eu sei que ele está em Community (Comunidade).<br />
Provavelmente Community não está habilitado no seu /etc/pacman.conf. Simplesmente descomente as linhas correspondentes.<br />
==Foo, no AUR está desatualizado, o que eu faço?==<br />
Para começar você deve marcá-lo como out-to-date (desatualizado). Se ele continuar desatualizado por um tempo considerável, a melhor coisa a fazer é enviar um email ao mantenedor do pacote. Se não receber resposta do mantenedor você pode solicitar a um TU que coloque o PKGBUILD como órfão (orphan), se estiver disposto a mantê-lo você mesmo.<br />
==Eu tenho um PKGBUILD que gostaria de submeter, alguém poderia verificá-lo para ver se há algum erro?==<br />
Se você gostaria de ter seu PKGBUILD comentado, poste-o na Lista de Email do AUR para obter retorno dos TUs e membros do AUR.<br />
Você pode também obter ajuda da turma do [[ArchChannel|canal irc]]: irc.freenode.net #archlinux<br />
<br />
==Foo, no AUR, não compila quando uso-o com makepkg, o que devo fazer?==<br />
Bem, primeiramente certifique-se de fazer um pacman -Syu antes de compilar qualquer coisa com makepkg já que o problema pode ser que seu sistema não esteja atualizado.<br />
Se não for isso reporte o problema ao mantenedor.</div>Neotulihttps://wiki.archlinux.org/index.php?title=ArchWiki:News&diff=21515ArchWiki:News2007-03-03T16:54:56Z<p>Neotuli: </p>
<hr />
<div>[[Category:About Arch (English)]]<br />
[[Category:General (English)]]<br />
{{News|03/02/2007 - New Wiki Skin|<br />
I've changed the wiki skin to the one used over at http://wiki.archlinuxfr.org (and formerly used on the german community's site). It is much less cluttered than the previous skin and fits the theme on the rest of our pages better. Enjoy.|--[[User:Neotuli|simo]] 15:53, 2 March 2007 (EST)<br />
}}<br />
{{News|01/21/2007 - Wiki upgrade|<br />
The mediawiki running Archwiki has been upgraded. Please report any issues on the [[ArchWiki:Bug_reports|bug report page]].|<br />
--[[User:Neotuli|simo]] 19:47, 21 January 2007 (PST)<br />
}}<br />
{{News|11/13/2006 - Wiki restructuring| <br />
We officially announce the start of grand wiki restructuring. The project is coordinated by [[User:Dusty|Dusty]], [[User:Foxbunny|foxbunny]], and [[User:Tardo|tardo]]. Project details are constantly updated on the [[Priority Todo]] page. Contact any of [[ContactList|these people]] if you want to participate in the project.|<br />
--[[User:Foxbunny|foxbunny]] 08:26, 13 November 2006 (PST)<br />
}}<br />
<br />
{{News|07/24/2005 - Wiki Migration is done!| <br />
The Great Wiki Migration has come to and end. There are still a few pages that need migration, but they are translation pages (language in other languages). You can find a link for them off the migration page locate at [[Migration Chunks!]]|<br />
--[[User:Cactus|cactus]] 15:49, 24 Jul 2005 (EDT)<br />
}}<br />
<br />
{{News|07/17/2005 - ArchWiki rolls again| <br />
The ArchLinux Wiki is alive again! Look for lots of new content to spring forth, as the Wiki will hopefully perform better, and be easier to use.|<br />
--[[User:Cactus|cactus]] 05:17, 17 Jul 2005 (EDT)<br />
}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=ArchWiki:Administrators&diff=21463ArchWiki:Administrators2007-03-02T20:58:15Z<p>Neotuli: </p>
<hr />
<div>[[Category:ArchWiki Help (English)]]<br />
'''If you have any question or suggestion contact one the members:'''<br />
<br />
* '''[[User:Rasat |Rasat]]''' (Markku) - rasat@user-contributions.org: Wiki moderator <br />
* '''[[User:Dusty |Dusty]]''' (Dusty) - dusty@buchuki.com: Wiki moderator and Catalyst<br />
* '''[[User:Gyroplast |Gyroplast]]''' (Dennis) - dennis@archlinux.org: Official ArchLinux Documentation Leader<br />
* '''[[User:Dp |Dp]]''' (Damir) - damir@archlinux.org: Wiki Structure, Navigation and i18n support<br />
* '''[[User:Foxbunny |foxbunny]]''' (Branko) - fox2bunny@yahoo.co.uk : Wiki Structure and Navigation<br />
* '''[[User:Snowman |Snowman]]''' (Eric) - belanger@ASTRO.UMontreal.CA : Wiki Structure and Navigation<br />
* '''[[User:Neotuli |Neotuli]]''' (Simo) - simo@archlinux.org: Low-Level wiki admin, bugs, upgrades, etc.</div>Neotulihttps://wiki.archlinux.org/index.php?title=ArchWiki:News&diff=21460ArchWiki:News2007-03-02T20:53:00Z<p>Neotuli: </p>
<hr />
<div>[[Category:About Arch (English)]]<br />
[[Category:General (English)]]<br />
{{News|03/02/2007 - New Wiki Skin|<br />
I've changed the wiki skin to the one used over at http://wiki.archlinuxfr.org . It is much less cluttered than the previous skin and fits the theme on the rest of our pages better. Enjoy.|--[[User:Neotuli|simo]] 15:53, 2 March 2007 (EST)<br />
}}<br />
{{News|01/21/2007 - Wiki upgrade|<br />
The mediawiki running Archwiki has been upgraded. Please report any issues on the [[ArchWiki:Bug_reports|bug report page]].|<br />
--[[User:Neotuli|simo]] 19:47, 21 January 2007 (PST)<br />
}}<br />
{{News|11/13/2006 - Wiki restructuring| <br />
We officially announce the start of grand wiki restructuring. The project is coordinated by [[User:Dusty|Dusty]], [[User:Foxbunny|foxbunny]], and [[User:Tardo|tardo]]. Project details are constantly updated on the [[Priority Todo]] page. Contact any of [[ContactList|these people]] if you want to participate in the project.|<br />
--[[User:Foxbunny|foxbunny]] 08:26, 13 November 2006 (PST)<br />
}}<br />
<br />
{{News|07/24/2005 - Wiki Migration is done!| <br />
The Great Wiki Migration has come to and end. There are still a few pages that need migration, but they are translation pages (language in other languages). You can find a link for them off the migration page locate at [[Migration Chunks!]]|<br />
--[[User:Cactus|cactus]] 15:49, 24 Jul 2005 (EDT)<br />
}}<br />
<br />
{{News|07/17/2005 - ArchWiki rolls again| <br />
The ArchLinux Wiki is alive again! Look for lots of new content to spring forth, as the Wiki will hopefully perform better, and be easier to use.|<br />
--[[User:Cactus|cactus]] 05:17, 17 Jul 2005 (EDT)<br />
}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=Linux_conferences&diff=19808Linux conferences2007-01-23T23:46:03Z<p>Neotuli: Add a link to some demos from linuxtag 2005</p>
<hr />
<div>[[Category:About Arch (English)]]<br />
[[Category:General (English)]]<br />
<br />
The idea behind this page is to make a list of big Linux conferences at which we'd like to have Arch Linux represented. The idea is that we can all contribute to it and coordinate on the dates, details, and who's going.<br />
<br />
Please contribute openly as you like.<br />
<br />
==Conferences==<br />
* [[Linux Kongress]] 2005<br /><br />
University of Hamburg, Germany<br /><br />
October 11-14, 2005<br /><br />
[http://www.linux-kongress.org/2005/]<br />
<br />
* [[Linux World Expo]] 2006<br /><br />
Boston, MA<br /><br />
April 3-5, 2006<br /><br />
[http://www.linuxworldexpo.com/]<br />
<br />
* [[LinuxTag]] 2006<br /><br />
Wiesbaden, Germany<br /><br />
May 3-6, 2006<br /><br />
[http://www.linuxtag.org]<br />
<br />
===Notes about conference preparation===<br />
A few notes about conference preparation:<br />
* Make banners. Most likely the information will have changed enough from the last conference to not be able to use the old ones. Banners add a nice look to the drab, boring, grey walls.<br />
* Book hotels '''early'''. If I'm not making myself clear enough, it needs to be as '''early as possible'''. Otherwise you may end up sleeping in a field...<br />
* Try to have at least 2 shifts of people. A booth our size (about 12 square meters) only needed about 4 people at a time. By breaking into two shifts, the booth will be cleaner, have more room in it, and people won't want to all go to lunch at the same time (half went to lunch before they came, the other half go to lunch when they leave).<br />
* Always make sure there's someone in the booth from opening to the end. This means that some people can't party with everyone else the night before. If you rotate the previously mentioned shifts, everyone will have a chance to party with everyone else.<br />
* Have display machines. Nothing is worse than trying to explain how something works to a visitor and not being able to show them.<br />
* Try to have some cool videos running on the display machines. Then they're much less boring when people walk by.<br />
** Examples of previously used demo videos: http://www.archlinux.org/~simo/demos/<br />
* If you plan on just laying CDs out on the table for anyone to grab, expect to give away a lot of CDs. We ended up having people take about 50 CDs a day, sometimes 2 or 3 at a time. If you plan on giving out CDs like this, look into getting a large bunch pressed: giving away burned CDs marked with a CD pen doesn't exactly look good.<br />
* If you plan on giving away flyers, have them printed before. Also, proof read them to make sure there aren't any silly spelling mistakes. You'll end up giving away more flyers than CDs.<br />
* Don't expect to get a lot of work done while you're in the booth. It's not exactly professional to sit there and force people to approach you because you're deep in some code somewhere.<br />
* Have a donation box. You will get donations.</div>Neotulihttps://wiki.archlinux.org/index.php?title=ArchWiki:News&diff=19700ArchWiki:News2007-01-22T03:48:23Z<p>Neotuli: </p>
<hr />
<div>{{News|01/21/2007 - Wiki upgrade|<br />
The mediawiki running Archwiki has been upgraded. Please report any issues on the [[ArchWiki:Bug_reports|bug report page]].|<br />
--[[User:Neotuli|simo]] 19:47, 21 January 2007 (PST)<br />
}}<br />
{{News|11/13/2006 - Wiki restructuring| <br />
We officially announce the start of grand wiki restructuring. The project is coordinated by [[User:Dusty|Dusty]], [[User:Foxbunny|foxbunny]], and [[User:Tardo|tardo]]. Project details are constantly updated on the [[Priority Todo]] page. Contact any of [[ContactList|these people]] if you want to participate in the project.|<br />
--[[User:Foxbunny|foxbunny]] 08:26, 13 November 2006 (PST)<br />
}}<br />
<br />
{{News|07/24/2005 - Wiki Migration is done!| <br />
The Great Wiki Migration has come to and end. There are still a few pages that need migration, but they are translation pages (language in other languages). You can find a link for them off the migration page locate at [[Migration Chunks!]]|<br />
--[[User:Cactus|cactus]] 15:49, 24 Jul 2005 (EDT)<br />
}}<br />
<br />
{{News|07/17/2005 - ArchWiki rolls again| <br />
The ArchLinux Wiki is alive again! Look for lots of new content to spring forth, as the Wiki will hopefully perform better, and be easier to use.|<br />
--[[User:Cactus|cactus]] 05:17, 17 Jul 2005 (EDT)<br />
}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=ArchWiki:News&diff=19699ArchWiki:News2007-01-22T03:47:50Z<p>Neotuli: </p>
<hr />
<div>{{News|01/21/2007 - Wiki upgrade|<br />
The mediawiki running Archwiki has been upgraded. Please report any issues on the [[ArchWiki:Bug_reports|bug report page]].<br />
--[[User:Neotuli|simo]] 19:47, 21 January 2007 (PST)<br />
}}<br />
{{News|11/13/2006 - Wiki restructuring| <br />
We officially announce the start of grand wiki restructuring. The project is coordinated by [[User:Dusty|Dusty]], [[User:Foxbunny|foxbunny]], and [[User:Tardo|tardo]]. Project details are constantly updated on the [[Priority Todo]] page. Contact any of [[ContactList|these people]] if you want to participate in the project.|<br />
--[[User:Foxbunny|foxbunny]] 08:26, 13 November 2006 (PST)<br />
}}<br />
<br />
{{News|07/24/2005 - Wiki Migration is done!| <br />
The Great Wiki Migration has come to and end. There are still a few pages that need migration, but they are translation pages (language in other languages). You can find a link for them off the migration page locate at [[Migration Chunks!]]|<br />
--[[User:Cactus|cactus]] 15:49, 24 Jul 2005 (EDT)<br />
}}<br />
<br />
{{News|07/17/2005 - ArchWiki rolls again| <br />
The ArchLinux Wiki is alive again! Look for lots of new content to spring forth, as the Wiki will hopefully perform better, and be easier to use.|<br />
--[[User:Cactus|cactus]] 05:17, 17 Jul 2005 (EDT)<br />
}}</div>Neotulihttps://wiki.archlinux.org/index.php?title=Arch_package_guidelines&diff=14388Arch package guidelines2006-07-22T18:51:38Z<p>Neotuli: </p>
<hr />
<div>[[Category:Package Management]] <br />
<h3 id="guidelines">Package Standards</h3><br />
<br />
<p><br />
When building packages for Arch Linux, you should <strong>adhere<br />
to the package guidelines</strong> below, especially if<br />
you would like to <strong>contribute</strong> your new package<br />
to Arch Linux.<br />
</p><br />
<br />
<h4>Package Naming</h4><br />
<br />
<ul><br />
<li><br />
Package names should consist of <strong>alphanumeric characters<br />
only</strong>; all letters should be<br />
<strong>lowercase</strong>.<br />
</li><br />
<li><br />
Package versions <strong>should be the same as the version<br />
released by the author</strong>. Versions can include<br />
letters if need be (eg, nmap's version is 2.54BETA32).<br />
<strong>Version tags may not include hyphens!</strong> Letters,<br />
numbers, and periods only.<br />
</li><br />
<br />
<li><br />
Package releases are <strong>specific to Arch Linux<br />
packages</strong>. These allow users to differentiate<br />
between newer and older package builds. When a new package<br />
version is first released, the <strong>release count starts at<br />
1</strong>. Then as fixes and optimizations are made,<br />
the package will be <strong>re-released</strong> to the AL<br />
public and the <strong>release number will increment</strong>.<br />
When a new version comes out, the release count resets to 1.<br />
Package release tags follow the <strong>same naming<br />
restrictions as version tags</strong>.<br />
</li> <br />
</ul> <br />
<br />
<h4>Directories</h4><br />
<ul><br />
<li><br />
<strong>Configuration files</strong> should be placed in the<br />
<code>/etc</code> directory. If there's more than one<br />
configuration file, it's customary to <strong>use a<br />
subdirectory</strong> in order to keep the<br />
<code>/etc</code> area as clean as possible. Use<br />
<code>/etc/{pkgname}/</code> where <code>{pkgname}</code> is<br />
the name of your package (or a suitable alternative, eg, apache<br />
uses <code>/etc/httpd/</code>). <br />
</li><br />
<br />
<li><br />
Package files should follow these <br />
<strong>general directory guidelines</strong>:<br />
</li> <br />
<br />
<table cellspacing="1" ><br />
<tr><br />
<td><code>/etc</code></td><br />
<td style="padding-left: 1em;"><br />
<strong>System-essential</strong> configuration files<br />
</td><br />
<br />
</tr><br />
<tr><br />
<td><code>/usr/bin</code></td><br />
<td style="padding-left: 1em;">Application binaries</td><br />
</tr><br />
<tr><br />
<td><code>/usr/sbin</code></td><br />
<br />
<td style="padding-left: 1em;">System binaries</td><br />
</tr><br />
<tr><br />
<td><code>/usr/lib</code></td><br />
<td style="padding-left: 1em;">Libraries</td><br />
</tr><br />
<tr><br />
<br />
<td><code>/usr/include</code></td><br />
<td style="padding-left: 1em;">Header files</td><br />
</tr><br />
<tr><br />
<td><code>/usr/lib/{pkg}</code></td><br />
<td style="padding-left: 1em;">Modules, plugins, etc.</td><br />
</tr><br />
<br />
<tr><br />
<td><code>/usr/man</code></td><br />
<td style="padding-left: 1em;">Manpages</td><br />
</tr><br />
<tr><br />
<td><code>/usr/share/{pkg}</code></td><br />
<td style="padding-left: 1em;">Application data</td><br />
<br />
</tr><br />
<tr><br />
<td><code>/etc/{pkg}</code></td><br />
<td style="padding-left: 1em;">Configuration files for <code>{pkg}</code></td><br />
</tr><br />
<tr><br />
<td><code>/opt</code></td><br />
<br />
<td style="padding-left: 1em;"><br />
Large self-contained packages such as KDE, Mozilla,<br />
etc.<br />
</td><br />
</tr><br />
</table><br />
</ul><br />
<br />
<h4>makepkg Duties</h4><br />
<br />
<p><br />
When you use makepkg to build a package for you, it does the<br />
following automatically:<br />
</p><br />
<br />
<ol><br />
<li><br />
Checks if package <strong>dependencies</strong> are installed <br />
</li><br />
<li><br />
<strong>Downloads source</strong> files from servers<br />
</li><br />
<br />
<li><br />
<strong>Unpacks</strong> source files<br />
</li><br />
<li><br />
Does any necessary <strong>patching</strong><br />
</li><br />
<li><br />
<br />
<strong>Builds</strong> the software and installs it in a fake<br />
root<br />
</li><br />
<li><br />
<strong>Removes</strong> <code>/usr/doc</code>,<br />
<code>/usr/info</code>, <code>/usr/share/doc</code>, and<br />
<code>/usr/share/info</code> from the package<br />
</li><br />
<br />
<li><br />
<strong>Strips</strong> symbols from binaries<br />
</li><br />
<li><br />
<strong>Strips</strong> debugging symbols from libraries<br />
</li><br />
<li><br />
Generates the <strong>package meta file</strong> which is<br />
included with each package<br />
</li><br />
<br />
<li><br />
<strong>Compresses</strong> the fake root into the package file<br />
</li><br />
<li><br />
<strong>Stores</strong> the package file in the configured<br />
destination directory<br />
(<span title="Current Working Directory" style="border-bottom:1px dotted">cwd</span> by<br />
default)<br />
</li><br />
<br />
</ol><br />
<br />
<h4>Package Etiquette</h4><br />
<br />
<ul><br />
<li>Packages should <strong>never</strong> be installed to <code>/usr/local</code></li><br />
<li><br />
<strong>Do not introduce new variables</strong> into<br />
your <code>PKGBUILD</code> build scripts, unless the package cannot be built without doing so, as these could<br />
possibly <strong>conflict</strong> with variables used<br />
in makepkg itself.<br />
<br />
If a new variable is absolutely required,<br />
<strong>prefix the variable name with an underscore</strong> (<code>_</code>) e.g<br />
<pre>_customvariable=</pre><br />
<br />
The AUR cannot detect the use of custom variables and so cannot use them in substitutions. This can most often be seen in the source array e.g.<br />
<pre>http://dl.sourceforge.net/sourceforge/directxwine/$patchname.$patchver.diff.bz2</pre><br />
Such a situation defeats the effective functionality of the AUR.<br />
</li><br />
<br />
<li><br />
<strong>Avoid</strong> using <code>/usr/libexec/</code> for<br />
anything. Use <code>/usr/lib/{pkg}</code> instead.<br />
</li><br />
<li><br />
The <code>packager</code> field from the package meta file can be<br />
<strong>customized</strong> by the package builder by modifying<br />
the appropriate option in the <code>/etc/makepkg.conf</code><br />
<br />
file, or alternatively by exporting the <code>PACKAGER</code><br />
environment variable before building packages with<br />
<code>makepkg</code>:<br />
<pre># export PACKAGER="John Doe@your.email"</pre><br />
</li><br />
<li>All<br />
important messages should be echoed during install using an <strong>.install file</strong>. For<br />
example, if a package needs extra setup to work, directions should be included. </li><br />
<li>Any <strong>optional dependencies</strong> that aren't<br />
needed to run the package or have it generally function shouldn't be<br />
included, but a warning message inside the .install file should echo<br />
something like: "To enable SMB support, download the Samba package."</li><br />
<li>When creating a <strong>package description</strong> for a package, do not include<br />
the package name in a self-referencing way. For example, "Nedit is a text editor for X11" could be simplified to "A text editor for X11". Also try to keep the descriptions to ~80 characters or less.</li><br />
</ul><br />
<h4>Licenses</h4><br />
The license array is being implemented little by little in the official repos, and it may be used in your packages as well. You can use it as follows:<br />
<ul><br />
<li>A licenses package will be created in [current] that stores common (to be defined later) licenses in /usr/share/licenses/common ie. /usr/share/licenses/common/GPL. If a package is licensed under one of these licenses, the licenses variable will be set to the directory name e.g. license="GPL"</li><br />
<li>If the appropriate license is not included in the official licenses package, several things must be done:<br />
<ol><br />
<li>The license file(s) should be included in /usr/share/licenses/$pkgname/ e.g. /usr/share/licenses/dibfoo/COPYING.</li><br />
<li>If the source tarball does NOT contain the license details and the license is only displayed on a website for example, then you need to copy the license to a file and include it. Remember to call it something appropriate too.<br />
<li>Add 'custom' to the licenses array. Optionally, you can replace 'custom' with 'custom:"name of license"'.</li><br />
</ol></li><br />
<li>Once a licenses is used in two or more packages in an official repo, including [community], it becomes common</li><br />
<li>The MIT, BSD and Python licenses are special cases and cannot be included in the 'common' licenses pkg. For the sake of the license variable, it's treated like a common license (license="BSD", license="MIT" or license="Python") but for the sake of the filesystem, it's a custom license, because each one has its own copyright line. Each MIT, BSD or Python licensed package should have its unique license stored in /usr/share/licenses/$pkgname/.</li><br />
<li>Some packages may not be covered by a single license. In these cases multiple entries may be made in the license array e.g. license=("GPL" "custom:some commercial license"). For the majority of packages these licenses apply in different cases, as opposed to applying at the same time. When pacman gets the ability to filter on licenses (so you can say, "I only want GPL and BSD licensed software") dual (or more) licenses will be treated by pacman using OR, rather than AND logic, thus pacman will consider the above example as GPL licensed software, regardless of the other licenses listed.</li></ul><br />
<br />
<h4>Submitting Packages</h4><br />
<br />
<p>Note the following before submitting any packages:</p><br />
<br />
<ol><br />
<li><br />
To ensure the security of pkgs submitted to the AUR please <strong>ensure</strong> that you have correctly filled the <code>md5sum</code> field. The <code>md5sum</code>'s can be generated using the <code>makepkg -g</code> command.<br />
</li><br />
<li><br />
Please <strong>add a comment line</strong> to the top of your<br />
<code>PKGBUILD</code> file that follows this format:<br />
<br />
<pre># Contributor: Your Name <your.email></pre><br />
</li><br />
<li><br />
Verify the package <strong>dependencies</strong> (eg, run<br />
<code>ldd</code> on dynamic executables, check tools required<br />
by scripts, etc).<br />
<br />
The TU team <strong>strongly</strong> recommend the use of the<br />
<code>namcap</code> utility, written by Jason Chu (jason@archlinux.org), to analyze the<br />
sanity of your package. <code>namcap</code> will tell you about<br />
bad permissions, missing dependencies, un-needed dependencies,<br />
and other common mistakes. You can install the<br />
<code>namcap</code> package with <code>pacman</code>.<br />
<br />
Remember <code>namcap</code> can be used to check both pkg.tar.gz files and PKGBUILDs<br />
</li><br />
<li> <strong>Dependencies</strong><br />
are the most common packaging error. Namcap can help detect them, but<br />
it is not always correct. Verify dependencies by looking at source<br />
documentation and the program website. </li><br />
<li><br />
All files uploaded to the AUR should be contained in a <strong>compressed tar<br />
file</strong> containing a directory with the <strong><code>PKGBUILD</code></strong> and <strong>additional build files</strong> (patches, install, ...) in it.<br />
<pre>foo/PKGBUILD<br />
foo/foo.install<br />
foo/foo_bar.diff<br />
foo/foo.rc.conf</pre><br />
The archive name should contain the name of the package<br />
e.g. foo.tar.gz<br />
<br />
The tarball <strong>should not</strong> contain the binary tarball created by makepkg, nor should it contain the filelist<br />
</li><br />
<br />
</ol><br />
<br />
<h3>Additional Guidelines</h3><br />
Be sure to read the above guidelines first - important points are listed on this page that will not be repeated in the following guideline pages. These specific guidelines are intended as an addition to the standards listed on this page.<br />
<br />
<h4>CVS/SVN Packages</h4><br />
Please see the [[Arch CVS & SVN PKGBUILD guidelines]]<br />
<br />
<h4>Java Packages</h4><br />
Please see the [[Java Package Guidelines]]</div>Neotulihttps://wiki.archlinux.org/index.php?title=Arch_IRC_channels&diff=14317Arch IRC channels2006-07-19T15:58:18Z<p>Neotuli: </p>
<hr />
<div>[[Category:Help]]<br />
__NOTOC__<br />
The official Archlinux channel is '''#archlinux''' on '''[http://www.freenode.net/ irc.freenode.net]''' (what is [http://www.irchelp.org/ IRC]?).<br />
If you have questions that cannot be answered by RTFM, join '''#archlinux''' and ask there.<br />
<br />
If you like, stay some time to help others by answering some questions yourself. Or even stay permanently :-)<br />
<br />
Use the above shown connection data to join with any IRC-client like [http://www.irssi.org/ irssi], [http://www.xchat.org/ XChat],<br />
[http://gaim.sourceforge.net/ Gaim] or [http://www.hacksrus.com/~ginda/chatzilla/ ChatZilla]. We collect some fortunes on the [[Wall of Quotes]].<br />
<br />
= Channel Guidelines =<br />
==after:==<br />
* When you've been served well, stay long & prosper to '''help others''' (in the channel and add to MuttWiki)!<br />
<br />
==before:==<br />
* Check '''google''', '''[http://bbs.archlinux.org the forums]''', '''[http://bugs.archlinux.org flyspray]''' and '''[[:Category:HowTos|The Wiki]]''' before you ask.<br />
* If you've '''already found''' the answers on your own by now, then '''tell us''' which docs helped you (not?).<br />
* Otherwise, if you want good & fast answers, ask '''[http://www.catb.org/~esr/faqs/smart-questions.html smart questions]'''<br />
** No mindreading here, '''state most specifically''': expected result(s) first, the ones you get, and then '''all''' circumstantial info.<br />
** Quality of answer won't exceed quality of question, you decide how helpful you are to yourself.<br />
<br />
==while:==<br />
* Just '''ask your stuff''', don't ask if we're "alive"!<br />
* '''Wait''' some time: eventually, someone will answer, don't count on instant reaction.<br />
* Be '''supportive''': we can't read minds, so be specific! See "smart-questions" above!<br />
** State your goal first, too, maybe you chose the wrong way.<br />
* Show '''commitment''': this is not a service hotline, this is a do-it-yourself environment.<br />
** Look up references yourself, use existing docs, learn to help yourself.<br />
* Be '''patient''' (with yourself & fellows): answers are favours, not your right.<br />
** You are supposed to do the actual work, you get advice and pointers.<br />
<br />
* '''Don't flood''' the channel by pasting lots of lines (up to 4 lines is ok). If you have to paste a lot of lines:<br />
** use a '''nopaste'''-website and post the URL to '''#archlinux''' channel (eg. [http://www.pastebin.com pastebin]).<br />
* Disable '''auto-away''' messages & '''nick-changes'''! Use the '''silent''' <tt>/away</tt> feature of your client manually, nothing else!<br />
* Last, but not least - keep it '''on topic'''.<br />
<br />
= Channel Statistics =<br />
* [[User:Brain0|Brain0]] also maintains the [[ArchMap|ArchMap]] for Google Earth. Add yourself!<br />
<br />
= Channel Addicts =<br />
<br />
These people spend far to much time in #archlinux.<br />
<br />
[[User:WillySilly|WillySilly]], c14n, [[User:Phrackture|phrakture]], Maveric-i686-, AqD, [[User:Stonecrest|stonecrest]], msg431, [[User:jMCg|jMCg]], syamajala, [[User:Mindtriggerz|mindtriggerz]], [[User:Codemac|codemac]]<br />
<br />
= Channel Regulars =<br />
<br />
shastry_, dadexter, Luke__, bitbull, ezech, jakob_, [[User:Iphitus|iphitus]], brain0, octan, dagnachew, [[User:Neotuli|neotuli]], [[User:Andrewski|andrewski]], Marco`, RedKennedy, criminy, gp_aaron, enightmare, [[User:Paniq|paniq]], [[User:Timtux|timtux]], [[User:Vardyr|Vardyr]], siimo, Aquila_Deu1, perry753, ZaxX, Infinitus, [[User:Xterminus|xterminus]]. LokeDK, shining_</div>Neotulihttps://wiki.archlinux.org/index.php?title=Arch_IRC_channels&diff=14312Arch IRC channels2006-07-19T15:03:09Z<p>Neotuli: /* Channel Regulars */</p>
<hr />
<div>[[Category:Help]]<br />
__NOTOC__<br />
The official Archlinux channel is '''#archlinux''' on '''[http://www.freenode.net/ irc.freenode.net]''' (what is [http://www.irchelp.org/ IRC]?).<br />
If you have questions that cannot be answered by RTFM, join '''#archlinux''' and ask there.<br />
<br />
If you like, stay some time to help others by answering some questions yourself. Or even stay permanently :-)<br />
<br />
Use the above shown connection data to join with any IRC-client like [http://www.irssi.org/ irssi], [http://www.xchat.org/ XChat],<br />
[http://gaim.sourceforge.net/ Gaim] or [http://www.hacksrus.com/~ginda/chatzilla/ ChatZilla]. We collect some fortunes on the [[Wall of Quotes]].<br />
<br />
= Channel Guidelines =<br />
==after:==<br />
* When you've been served well, stay long & prosper to '''help others''' (in the channel and add to MuttWiki)!<br />
<br />
==before:==<br />
* Check '''google''', '''[http://bbs.archlinux.org the forums]''', '''[http://bugs.archlinux.org flyspray]''' and '''[[:Category:HowTos|The Wiki]]''' before you ask.<br />
* If you've '''already found''' the answers on your own by now, then '''tell us''' which docs helped you (not?).<br />
* Otherwise, if you want good & fast answers, ask '''[http://www.catb.org/~esr/faqs/smart-questions.html smart questions]'''<br />
** No mindreading here, '''state most specifically''': expected result(s) first, the ones you get, and then '''all''' circumstantial info.<br />
** Quality of answer won't exceed quality of question, you decide how helpful you are to yourself.<br />
<br />
==while:==<br />
* Just '''ask your stuff''', don't ask if we're "alive"!<br />
* '''Wait''' some time: eventually, someone will answer, don't count on instant reaction.<br />
* Be '''supportive''': we can't read minds, so be specific! See "smart-questions" above!<br />
** State your goal first, too, maybe you chose the wrong way.<br />
* Show '''commitment''': this is not a service hotline, this is a do-it-yourself environment.<br />
** Look up references yourself, use existing docs, learn to help yourself.<br />
* Be '''patient''' (with yourself & fellows): answers are favours, not your right.<br />
** You are supposed to do the actual work, you get advice and pointers.<br />
<br />
* '''Don't flood''' the channel by pasting lots of lines (up to 4 lines is ok). If you have to paste a lot of lines:<br />
** use a '''nopaste'''-website and post the URL to '''#archlinux''' channel (eg. [http://www.pastebin.com pastebin]).<br />
* Disable '''auto-away''' messages & '''nick-changes'''! Use the '''silent''' <tt>/away</tt> feature of your client manually, nothing else!<br />
<br />
= Channel Statistics =<br />
<br />
* [[User:MindTriggerz|MindTriggerz]] runs a bot which generates a [http://mindtriggerz.net/images/archlinux/archlinux-current.png graph of the channel social network].<br />
* [[User:Xterminus|Xterminus]] runs pirc on his irc logs nightly to generate some generic [http://charles.mauch.name/irc/archlinux.html stats].<br />
* [[User:Xterminus|Xterminus]] also maintains the [[ArchMap|ArchMap]]. Add yourself!<br />
<br />
= Channel Addicts =<br />
<br />
These people spend far to much time in #archlinux.<br />
<br />
[[User:WillySilly|WillySilly]], c14n, [[User:Phrackture|phrakture]], Maveric-i686-, AqD, [[User:Stonecrest|stonecrest]], msg431, [[User:jMCg|jMCg]], syamajala, [[User:Mindtriggerz|mindtriggerz]], [[User:Codemac|codemac]]<br />
<br />
= Channel Regulars =<br />
<br />
shastry_, dadexter, Luke__, bitbull, ezech, jakob_, [[User:Iphitus|iphitus]], brain0, octan, dagnachew, [[User:Neotuli|neotuli]], [[User:Andrewski|andrewski]], Marco`, RedKennedy, criminy, gp_aaron, enightmare, [[User:Paniq|paniq]], [[User:Timtux|timtux]], [[User:Vardyr|Vardyr]], siimo, Aquila_Deu1, perry753, ZaxX, Infinitus, [[User:Xterminus|xterminus]]. LokeDK, shining_</div>Neotulihttps://wiki.archlinux.org/index.php?title=DVD_Ripping_(%E7%AE%80%E4%BD%93%E4%B8%AD%E6%96%87)&diff=13035DVD Ripping (简体中文)2006-05-14T19:27:30Z<p>Neotuli: rm spam, spammer gamma8</p>
<hr />
<div>[[Category:CD/DVD (简体中文)]]<br />
<br />
{{i18n_links_start}}<br />
{{i18n_entry|English|DVD Ripping}}<br />
{{i18n_entry|简体中文|DVD Ripping (简体中文)}}<br />
{{i18n_links_end}}<br />
<br />
== 使用 DVD::Rip ==<br />
=== 软件 ===<br />
您需要先安装以下几个软件:<br />
* '''dvd::rip''': 前端软件和编码转换器,用于压缩和编码<br />
* '''libdv''': 对DVD视频的软件解码器<br />
* '''xvidcore''': 用于把DVD压缩为XVid格式(DivX格式外的另一选择)<br />
* '''divx4linux''': 用于把DVD压缩为DivX格式(5.10测试版)<br />
<br />
=== 配置 ===<br />
dvd::rip的配置并不难。若您需要帮助,可参阅[http://www.exit1.org/dvdrip/doc/gui-gui_pref.cipp]。<br />
<br />
=== 编码器的设置 ===<br />
* XVid: 安装后立即就可以使用了。<br />
* DivX: 如果 dvd::rip 抱怨说无法初始化 Divx 编码器,则可能是因为缺失了 libstdc++-libc6.2-2.so.3 文件。这已是老早前的问题了,在这个网页 [http://home.nyc.rr.com/computertaijutsu/arch.html] 上有讲到。(您可以从这个网页中下载到该文件,并把它放到/usr/lib里)<br />
* 然后您可以按此菜单顺序,在dvd::rip里选择您喜好的解码器:参数->杂项->默认视频解码器 (divx4linux使用DivX5作为默认视频解码器)(译者注:俺没有中文界面,所以这里的菜单上的名字可能和您在dvd::rip里看到的不一样,如果你确实发现如此,请直接校正本文,谢谢)<br />
<br />
PS: 若您想知道关于编码器之间相互比较的更详细信息,请参阅以下链接:<br />
* [http://www.doom9.net doom9.net]<br />
* [http://bbs.archlinux.org/viewtopic.php?p=55417#55417 forum post on archlinux]<br />
<br />
=== 压缩 ===<br />
点了按钮后,您等着就行啦!<br />
<br />
== 使用 Mencoder ==<br />
既然您可能已经安装并使用MPlayer来看DVD了(因此你可能要用到libdvdread等),您可以从命令行压缩DVD。这同时也需要用到MP3编码器。<br />
<br />
=== Bash 脚本 ===<br />
这个是我用来压缩DVD的脚本,它虽不完美,但在我这它工作正常。这个脚本并不能完成象剪接这样的高级功能,但它能保持原有画面的比例。<br />
<br />
<pre><br />
#!/bin/sh<br />
<br />
# Dvd2Avi 0.2<br />
# Only does one title at a time, but "avimerge" from Transcode<br />
# can sort it from there.<br />
<br />
# by yyz<br />
<br />
echo -n "Enter the name of output file (without extension):"<br />
read FILE<br />
<br />
echo -n "Enter the title you wish to rip:"<br />
read TITLE<br />
<br />
echo -n "Select a quality level (h/n/l)[[n]]:"<br />
read Q<br />
<br />
if [[ -z $Q ]];then <br />
# If no quality passed, default to normal<br />
Q=n<br />
fi<br />
<br />
if [[ $Q = h ]]; then <br />
# If h passed, use high quality<br />
mencoder dvd://$TITLE -alang en -oac mp3lame -lameopts br=320:cbr -ovc lavc -lavcopts vcodec=mpeg4:vhq -vop scale -zoom -xy 800 -o $FILE.avi<br />
exit 0<br />
fi<br />
<br />
if [[ $Q = n ]]; then <br />
# If n passed, use normal quality (recommended)<br />
mencoder dvd://$TITLE -alang en -oac mp3lame -lameopts br=160:cbr -ovc lavc -lavcopts vcodec=mpeg4:vhq -vop scale -zoom -xy 640 -o $FILE.avi<br />
exit 0<br />
fi<br />
<br />
if [[ $Q = l ]]; then <br />
# If l passed, use low quality. not really worth it, <br />
# hardly any smaller but much crappier<br />
mencoder dvd://$TITLE -alang en -oac mp3lame -lameopts br=96:vbr -ovc lavc -lavcopts vcodec=mpeg4:vhq -vop scale -zoom -xy 320 -o $FILE.avi<br />
exit 0<br />
fi<br />
</pre><br />
<br />
这是三个压缩质量等级的说明:<br />
* High: 画面宽800px,音频为320kbps的mp3<br />
* Normal: 画面宽640px,音频为160kbps的mp3<br />
* Low: 画面宽320px,音频为96kbps的mp3<br />
<br />
要使用此脚本,把它拷贝并粘贴到一个文件中(如dvdrip.sh),赋予执行权限 <code>chmod +x <file> </code>,然后执行它。<br />
<br />
希望此脚本对您来说并不太难懂。您可以随意更改它,以达到您所期望效果。想了解更多信息,请参阅<code>man mencoder</code>。<br />
<br />
=== Mencoder 的图形界面 ===<br />
如果您不喜欢使用命令行环境,或是想使用更多mencoder的功能选项,您还可以使用它的一些图形界面。<br />
<br />
MPlayer的 [http://www.mplayerhq.hu/homepage/design3/projects.html#mencoder_frontends 官方网站] 上有一个详尽的图形界面列表。</div>Neotulihttps://wiki.archlinux.org/index.php?title=Startup_files&diff=13034Startup files2006-05-14T19:26:07Z<p>Neotuli: rm spam, spammer gamma8</p>
<hr />
<div>== If you want to startup your computer to a DM(Desktop Manger. Like XDM, GDM, Entrance) or to a shell ==<br />
<br />
open /etc/inittab<br />
<br />
change the last line in the file to the DM of your choice.<br />
<br />
examples:<br />
<pre><br />
x:5:respawn:/opt/e17/sbin/entranced -nodaemon<br />
x:5:respawn:/opt/gnome/sbin/gdm -nodaemon<br />
x:5:respawn:/usr/X11R6/bin/xdm -nodaemon<br />
</pre><br />
<br />
Then you can set the first line in inittab to 5 to startup a DE as default or 3 to startup a shell(usually /bin/bash, you can set it by using chsh) as default.<br />
<br />
example:<br />
<pre><br />
id:5:initdefault:<br />
</pre><br />
<br />
You can also specify this one on GRUB cmd-line when you bootup by adding 'init single' (to not load any modules) 'init 3' or 'init 5'.<br />
<br />
== After INIT X on startup ==<br />
''explanation'': after you see INIT 3 (or5) when you startup your computer but before you have logged in: this file /etc/rc.local executes.<br />
<br />
== When /bin/bash is being used (through xterm or as login shell etc..) ==<br />
~/.bashrc executes and set's all the ENVIRONMENT VARIABLES for itself. You can put whatever you want here if you want it to startup each time you open an xterm etc.<br />
<br />
== if you run startx or xinit ==<br />
~/.xinitrc executes<br />
<br />
== XDM ==<br />
From the xdm man page:<br />
<pre><br />
First, the xdm configuration file should be set up. Make a directory<br />
(usually /usr/X11R6/lib/X11/xdm) to contain all of the relevant files.<br />
<br />
Here is a reasonable configuration file, which could be named xdm-con-<br />
fig:<br />
<br />
DisplayManager.servers: /usr/X11R6/lib/X11/xdm/Xservers<br />
DisplayManager.errorLogFile: /var/log/xdm.log<br />
DisplayManager*resources: /usr/X11R6/lib/X11/xdm/Xresources<br />
DisplayManager*startup: /usr/X11R6/lib/X11/xdm/Xstartup<br />
DisplayManager*session: /usr/X11R6/lib/X11/xdm/Xsession<br />
DisplayManager.pidFile: /usr/X11R6/lib/X11/xdm/xdm-pid<br />
DisplayManager._0.authorize: true<br />
DisplayManager*authorize: false<br />
<br />
Note that this file mostly contains references to other files. Note<br />
also that some of the resources are specified with ``*'' separating the<br />
components. These resources can be made unique for each different dis-<br />
play, by replacing the ``*'' with the display-name, but normally this<br />
is not very useful. See the Resources section for a complete discus-<br />
sion.<br />
</pre><br />
<br />
Note that these can also be in ~/.Xstartup and ~/.Xresources<br />
<br />
== DE startup files ==<br />
''explanation'': when you launch a DE, these files startup things for you.<br><br />
<br />
=== XFCE, GNOME, KDE ===<br />
~/Desktop/Autostart/*<br />
=== KDE ===<br />
~/.kde/Autostart<br />
=== Fluxbox === <br />
~/.fluxbox/startup<br />
<br />
== Arch Specific ==<br />
/etc/rc.conf: Among other things executes modules and the daemons(scripts) inside /etc/rc.d/ at bootup before you have logged in<br><br />
/etc/rc.d/* - configured deamons for the system.<br />
<br />
== Notes ==<br />
make sure the various startup files have execute permissions for your user. here's an example.<br />
<pre><br />
chmod a+rwx name-of-startup-file<br />
</pre></div>Neotulihttps://wiki.archlinux.org/index.php?title=Unofficial_user_repositories&diff=5318Unofficial user repositories2005-10-30T17:41:42Z<p>Neotuli: despam and update to reflect the AUR's existence, TURs don't exist anymore...</p>
<hr />
<div>== Why unofficial user repositories ==<br />
Since the AUR only allows users to upload PKGBUILD and other package build related files, but does not provide a means for distributing a binary package, a user may want to create a binary repository of their packages elsewhere.<br />
<br />
<br />
== The community repository, maintained by the TUs==<br />
<nowiki>[community]<br />
Server = ftp://ftp.archlinux.org/community/os/i686/<br />
</nowiki><br />
== List of PUR (unofficial user repositories) ==<br />
<nowiki> [cjdj]<br />
Server = http://www.cjdj.org/arch/pkg<br />
<br />
[effigies]<br />
Server = http://effigies.freelinuxhost.com/pacman/<br />
<br />
[hostile]<br />
Server = http://lanteau.homelinux.org/~lanteau/arch/hostile<br />
<br />
[vegai]<br />
Server = http://people.jyu.fi/~vpkaihla/arch<br />
<br />
[celti]<br />
Server = ftp://celti.a.la/archlinux/packages/i686/celti<br />
Server = http://celti.afraid.org/archlinux/packages/i686/celti/<br />
<br />
[archlinux-nl]<br />
Server = http://pkg.archlinux.nl<br />
<br />
[dma147]<br />
Server = http://arch.linux-stats.org/pkgs<br />
<br />
[Victor]<br />
Server = http://personales.ya.com/vmromanos/arch/pkgs<br />
<br />
[marfis]<br />
Server = http://arch.marfis.org/binaries<br />
<br />
[berkus]<br />
Server = http://arch.madfire.net<br />
<br />
[venox]<br />
Server = http://arch.lworks.org<br />
Server = http://arch.lworks.cjb.net/<br />
<br />
[fubar]<br />
Server = http://marcosaxo.madoka.be/files/arch<br />
<br />
[chao]<br />
Server = http://chao.ch/archiv/archlinux/i686/<br />
<br />
[shadowhand]<br />
Server = http://archpkg.wgilk.com/shadowhand<br />
<br />
<br />
</nowiki><br />
<br />
== Add your own repository to this list ==<br />
If you have your own repository, please add this to this list, so that all other users knows where to find your packages.</div>Neotuli