Hide options
developer archive 1 download
Oracle 10g developer cd 1 4shared.com ext: .rar 562 MB date: 2012-07-21
Source title: archive - 4shared.com - search and download
search.4shared.com
Video results for: developer archive 1 
dbdvrf #9 Debian Developer's Reference http://packages.debian.org/sid/developers-reference (More) http://packages.debian.org/sid/developers-reference - - and sparc architectures. Debian 2.2 added support for the powerpc and arm architectures. Debian 3.0 added support of five new architectures: ia64, hppa, s390, mips and mipsel. Information for developers and users about the specific ports are available at the Debian Ports web pages. 4.6.3. Packages There are two types of Debian packages, namely source and binary packages. Source packages consist of either two or three files: a .dsc file, and either a .tar.gz file or both an .orig.tar.gz and a .diff.gz file. If a package is developed specially for Debian and is not distributed outside of Debian, there is just one .tar.gz file which contains the sources of the program. If a package is distributed elsewhere too, the .orig.tar.gz file stores the so-called upstream source code, that is the source code that's distributed by the upstream maintainer (often the author of the software). In this case, the .diff.gz contains the changes made by the Debian maintainer. The .dsc file lists all the files in the source package together with checksums (md5sums) and some additional info about the package (maintainer, version, etc.). 4.6.4. Distributions The directory system described in the previous chapter is itself contained within distribution directories. Each distribution is actually contained in the pool directory in the top-level of the Debian archive itself. To summarize, the Debian archive has a root directory within an FTP server. For instance, at the mirror site, ftp.us.debian.org, the Debian archive itself is contained in /debian, which is a common location (another is /pub/debian). A distribution comprises Debian source and binary packages, and the respective Sources and Packages index files, containing the header information from all those packages. The former are kept in the pool/ directory, while the latter are kept in the dists/ directory of the archive (for backwards compatibility). 4.6.4.1. Stable, testing, and unstable There are always distributions called stable (residing in dists/ stable), testing (residing in dists/testing), and unstable (residing in dists/unstable). This reflects the development process of the Debian project. Active development is done in the unstable distribution (that's why this distribution is sometimes called the development distribution). Every Debian developer can update his or her packages in this distribution at any time. Thus, the contents of this distribution change from day to day. Since no special effort is made to make sure everything in this distribution is working properly, it is sometimes literally unstable. The testing distribution is generated automatically by taking packages from unstable if they satisfy certain criteria. Those criteria should ensure a good quality for packages within testing. The update to testing is launched twice each day, right after the new packages have been installed. See Section 5.13, The testing distribution . After a period of development, once the release manager deems fit, the testing distribution is frozen, meaning that the policies which control how packages move from unstable to testing are tightened. Packages which are too buggy are removed. No changes are allowed into testing except for bug fixes. After some time has elapsed, depending on progress, the testing distribution is frozen even further. Details of the handling of the testing distribution are published by the Release Team on debian-devel-announce. After the open issues are solved to the satisfaction of the Release Team, the distribution is released. Releasing means that testing is renamed to stable, and a new copy is created for the new testing, and the previous stable is renamed to oldstable and stays there until it is finally archived. On archiving, the contents are moved to archive.debian.org). This development cycle is based on the assumption that the unstable distribution becomes stable after passing a period of being in testing. Even once a distribution is considered stable, a few bugs inevitably remain — that's why the stable distribution is updated every now and then. However, these updates are tested very carefully and have to be introduced into the archive individually to reduce the risk of introducing new bugs. You can find proposed additions to stable in the proposed-updates directory. Those packages in proposed-updates that pass muster are periodically moved as a batch into the stable distribution and the revision level of the stable distribution is incremented (e.g., 3.0 becomes 3.0r1, 2.2r4 becomes 2.2r5, and so forth). Please refer to uploads to the stable distribution for details. Note that development under unstable continues during the freeze period, since the unstable distribution remains in place in parallel with testing. 4.6.4.2. More information (Less)
dbdvrf #14 Debian Developer's Reference http://packages.debian.org/sid/developers-reference (More) http://packages.debian.org/sid/developers-reference - - Bcc: pts-news@qa.debian.org Subject: Galeon 2.0 backported for woody X-PTS-Package: galeon Hello gnomers! I'm glad to announce that galeon has been backported for woody. You'll find everything here: ... Think twice before adding a news item to the PTS because you won't be able to remove it later and you won't be able to edit it either. The only thing that you can do is send a second news item that will deprecate the information contained in the previous one. 4.11. Developer's packages overview A QA (quality assurance) web portal is available at http:// qa.debian.org/developer.php which displays a table listing all the packages of a single developer (including those where theparty is listed as a co-maintainer). The table gives a good summary about the developer's packages: number of bugs by severity, list of available versions in each distribution, testing status and much more including links to any other useful information. It is a good idea to look up your own data regularly so that you don't forget any open bugs, and so that you don't forget which packages are your responsibility. 4.12. Debian's GForge installation: Alioth Alioth is a Debian service based on a slightly modified version of the GForge software (which evolved from SourceForge). This software offers developers access to easy-to-use tools such as bug trackers, patch manager, project/task managers, file hosting services, mailing lists, CVS repositories etc. All these tools are managed via a web interface. It is intended to provide facilities to free software projects backed or led by Debian, facilitate contributions from external developers to projects started by Debian, and help projects whose goals are the promotion of Debian or its derivatives. It's heavily used by many Debian teams and provides hosting for all sorts of VCS repositories. All Debian developers automatically have an account on Alioth. They can activate it by using the recover password facility. External developers can request guest accounts on Alioth. For more information please visit the following links: * http://wiki.debian.org/Alioth * http://wiki.debian.org/Alioth/FAQ * http://wiki.debian.org/ Alioth/PackagingProject * http://alioth.debian.org/ 4.13. Goodies for Developers 4.13.1. LWN Subscriptions Since October of 2002, HP has sponsored a subscription to LWN for all interested Debian developers. Details on how to get access to this benefit are in http://lists.debian.org/ debian-devel-announce/ 2002/10/msg00018.html. Chapter 5. Managing Packages This chapter contains information related to creating, uploading, maintaining, and porting packages. 5.1. New packages If you want to create a new package for the Debian distribution, you should first check the Work-Needing and Prospective Packages (WNPP) list. Checking the WNPP list ensures that no one is already working on packaging that software, and that effort isnot duplicated. Read the WNPP web pages for more information. Assuming no one else is already working on your prospective package, you must then submit a bug report (Section 7.1, Bug reporting ) against the pseudo-package wnpp describing your plan to create a new package, including, but not limiting yourself to, a description of the package, the license of the prospective package, and the current URL where it can be downloaded from. You should set the subject of the bug to ITP: foo -- short description, substituting the name of the new package for foo. The severity of the bug report must be set to wishlist. Please send a copy to [debian-devel@ lists.debian.org] by using the X-Debbugs-CC header (don't use CC:, because that way the message's subject won't indicate the bug number). If you are packaging so many new packages (]10) that notifying the mailing list in seperate messages is too disruptive, do send a summary after filing the bugs to the debian-devel list instead. This will inform the other developers about upcoming packages and will allow a review of your description and package name. Please include a Closes: bug#nnnnn entry in the changelog of the new package in order for the bug report to be automatically closed once the new package is installed in the archive (see Section 5.8.4, When bugs are closed by new uploads ). When closing security bugs include CVE numbers as well as the Closes: #nnnnn. This is useful for the security team to track vulnerabilities. If an upload is made to fix the bug before the advisory ID is known, it is encouraged to modify the historical changelog entry with the next upload. Even in this case, please include all available pointers to background information in the original changelog entry. There are a number of reasons why we ask maintainers to announce their intentions: * It helps the (potentially new) maintainer to tap into the experience of people (Less)
Adobe Dreamweaver Developer Toolbox 1 0 0 EN www clubedoparente com 4shared.com ext: .rar 5 MB date: 2012-12-18
Source title: archive - 4shared.com - search and download
search.4shared.com
Dark Fire Blue X UnNamed 2 2 1 dropbox.com ext: .zip 94 MB date: 2012-09-17
Source title: fire blue x and dark fire x (unnamed) [archive] - xda-developers
forum.xda-developers.com
Dark Fire X UnNamed 2 2 1 dropbox.com ext: .zip 93 MB date: 2012-09-17
Source title: fire blue x and dark fire x (unnamed) [archive] - xda-developers
forum.xda-developers.com
CallRecorder v 1 0 20 alpha 2 dropbox.com ext: .apk 171 KB date: 2012-09-16
Source title: 4|cmdline|sweep2wake|mpdecision|bad ass [archive] - xda-developers
forum.xda-developers.com
Sponsored results
Join Our Fan Page on Facebook!
About | Privacy | Cookies policy | Terms | DMCA Policy | Contact | Api
FilesTube lets you search for shared files from various file hosting sites like:
Uploaded.to, Rapidgator.net, Netload.in, 4shared.com, Extabit.com, Turbobit.net, Mediafire.com and many others.
Copyright 2013 © FilesTube.com, 514,761,976 files indexed
All sites 
