Re: Multimedia message (HAPPYTURKEYDAY.3gp) - November 29, 2008, 12:19 AM
- Length: 0:19
- Rating: ( ratings)
- Views:
- Author: NewYorkHunter
Video Cam Direct Upload
Re: Zombies.
- Length: 0:33
- Rating: ( ratings)
- Views:
- Author: JoeyHeartz
Tags: head in omgoctopus shoot the them zombies
Video Cam Direct Upload
Re: A Very Harmonious Reply To Pyrrho
- Length: 3:13
- Rating: ( ratings)
- Views:
- Author: pyrrho314
Tags: civilization future Harmonious human of overpopulation Pyrrho Reply societies To Very
Video Cam Direct Upload
my first try split screen and after effect method
- Length: 2:49
- Rating: ( ratings)
- Views:
- Author: tassapon
Tags: beautiful drum expert is life rockband2
I try to use this method of vdo editing (split screen) I use sony HDR SR10 to capture direct to my TV and iSight (from my iMac) to capture myself (with bad frame rate) and use Adobe After Effect to complete this.
Re: 51 things i found around my house.
- Length: 0:0
- Rating: ( ratings)
- Views:
- Author: mCount
Tags: 51 artichoke blink dudeneedaeaseonup found hurricaneaubrey larrysmash things whippet
Video Cam Direct Upload
Watch Direct Review - watchdirect.com
- Length: 0:15
- Rating: ( ratings)
- Views:
- Author: larryjob133
Tags: Direct Review Watch watchdirect.com
http://moneyreviewer.info/watchdirect.html Watch Direct Review - watchdirect.com
mere sapno ki rani.mp4
- Length: 4:13
- Rating: ( ratings)
- Views:
- Author: mrsovy
Tags: arassen best hindi ki mere rani sapno song top
Live n direct DJ Fouzer frm australia
dbdvrf #45 Debian Developer's Reference
- Length: 7:29
- Rating: ( ratings)
- Views:
- Author: h4ck3rm1k3
Tags: debian developers reference
http://packages.debian.org/sid/developers-reference - - to the original filename. Note that you don't need to depend on sharutils to get the uudecode program if you use perl's pack function. The code could look like uuencode-file: perl -ne 'print(pack "u", $$_);' $(file) ] $(file).uuencoded uudecode-file: perl -ne 'print(unpack "u", $$_);' $(file).uuencoded ] $(file) Chapter**7.**Beyond Packaging Debian is about a lot more than just packaging software and maintaining those packages. This chapter contains information about ways, often really critical ways, to contribute to Debian beyond simply creating and maintaining packages. As a volunteer organization, Debian relies on the discretion of its members in choosing what they want to work on and in choosing the most critical thing to spend their time on. 7.1.**Bug reporting We encourage you to file bugs as you find them in Debian packages. In fact, Debian developers are often the first line testers. Finding and reporting bugs in other developers' packages improves the quality of Debian. Read the instructions for reporting bugs in the Debian bug tracking system. Try to submit the bug from a normal user account at which you are likely to receive mail, so that people can reach you if they need further information about the bug. Do not submit bugs as root. You can use a tool like reportbug(1) to submit bugs. It can automate and generally ease the process. Make sure the bug is not already filed against a package. Each package has a bug list easily reachable at http:// bugs.debian.org/packagename Utilities like querybts( 1) can also provide you with this information (and reportbug will usually invoke querybts before sending, too). Try to direct your bugs to the proper location. When for example your bug is about a package which overwrites files from another package, check the bug lists for both of those packages in order to avoid filing duplicate bug reports. For extra credit, you can go through other packages, merging bugs which are reported more than once, or tagging bugs `fixed' when they have already been fixed. Note that when you are neither the bug submitter nor the package maintainer, you should not actually close the bug (unless you secure permission fromthe maintainer). From time to time you may want to check what has been going on with the bug reports that you submitted. Take this opportunity to close those that you can't reproduce anymore. To find out all the bugs you submitted, you just have to visit http:// bugs.debian.org/from:[your-email-addr]. 7.1.1.**Reporting lots of bugs at once (mass bug filing) Reporting a great number of bugs for the same problem on a great number of different packages *** i.e., more than 10 *** is a deprecated practice. Take all possible steps to avoid submitting bulk bugs at all. For instance, if checking for the problem can be automated, add a new check to lintian so that an error or warning is emitted. If you report more than 10 bugs on the same topic at once, it is recommended that you send a message to [ debian-devel@lists.debian.org] describing your intention before submitting the report, and mentioning the fact in the subject of your mail. This will allow other developers to verify that the bug is a real problem. In addition, it will help prevent a situation in which several maintainers start filing the same bug report simultaneously. Please use the programms dd-list and if appropriate whodepends (from the package devscripts) to generate a list of all affected packages, and include the output in your mail to [ debian-devel@lists.debian.org]. Note that when sending lots of bugs on the same subject, you should send the bug report to [maintonly@bugs.debian.org] so that the bug report is not forwarded to the bug distribution mailing list. 7.2.**Quality Assurance effort 7.2.1.**Daily work Even though there is a dedicated group of people for Quality Assurance, QA duties are not reserved solely for them. You can participate in this effort by keeping your packages as bug-free as possible, and as lintian-clean (see Section**A.2.1, ***lintian*** ) as possible. If you do not find that possible, then you should consider orphaning some of your packages (see Section**5.9.4, ***Orphaning a package* ** ). Alternatively, you may ask the help of other people in order to catch up with the backlog of bugs that you have (you can ask for help on [debian-qa@lists.debian.org] or [debian-devel@lists.debian.org]) . At the same time, you can look for co-maintainers (see Section**5.12, * **Collaborative maintenance*** ). 7.2.2.**Bug squashing parties From time to time the QA group organizes bug squashing parties to get rid of as many problems as possible. They are announced on [debian-devel-announce@ lists.debian.org] and the announcement explains which area will be the focus of the party: usually they focus on release critical bugs but it may happen
dbdvrf #38 Debian Developer's Reference
- Length: 7:35
- Rating: ( ratings)
- Views:
- Author: h4ck3rm1k3
Tags: debian developers reference
http://packages.debian.org/sid/developers-reference - - Maintainer scripts include the files debian/postinst, debian/ preinst, debian/prerm and debian/postrm. These scripts take care of any package installation or deinstallation setup which isn't handled merely by the creation or removal of files and directories. The following instructions supplement the Debian Policy. Maintainer scripts must be idempotent. That means that you need to make sure nothing bad will happen if the script is called twice where it would usually be called once. Standard input and output may be redirected (e.g. into pipes) for logging purposes, so don't rely on them being a tty. All prompting or interactive configuration should be kept to a minimum. When it is necessary, you should use the debconfpackage for the interface. Remember that prompting in any case can only be in the configure stage of the postinst script. Keep the maintainer scripts as simple as possible. We suggest you use pure POSIX shell scripts. Remember, if you do need any bash features, the maintainer script must have a bash shebang line. POSIX shell or Bash are preferred to Perl, since they enable debhelper to easily add bits to the scripts. If you change your maintainer scripts, be sure to test package removal, double installation, and purging. Be sure that a purged package is completely gone, that is, it must remove any files created, directly or indirectly, in any maintainer script. If you need to check for the existence of a command, you shoulduse something like if [ -x /usr/sbin/install-docs ]; then ... If you don't wish to hard-code the path of a command in your maintainer script, the following POSIX-compliant shell function may help: pathfind() { OLDIFS="$IFS" IFS=: for p in $PATH; do if [ -x "$p/$*" ]; then IFS="$OLDIFS" return 0 fi done IFS="$OLDIFS" return 1 } You can use this function to search $PATH for a command name, passed as an argument. It returns true (zero) if the command was found, and false if not. This is really the most portable way, since command -v, type, and which are not POSIX. While which is an acceptable alternative, since it is from the required debianutils package, it's not on the root partition. That is, it's in /usr/bin rather than /bin, so one can't use it in scripts which are run before the /usr partition is mounted. Most scripts won't have this problem, though. 6.5.**Configuration management with debconf Debconf is a configuration management system which can be used by all the various packaging scripts (postinst mainly) to request feedback from the user concerning how to configure the package. Direct user interactions must now be avoided in favor of debconf interaction. This will enable non-interactive installations in the future. Debconf is a great tool but it is often poorly used. Many common mistakes are listed in the debconf-devel(7) man page. It is something that you must read if you decide to use debconf. Also, we document some best practices here. These guidelines include some writing style and typography recommendations, general considerations about debconf usage as well as more specific recommendations for some parts of the distribution (the installation system for instance). 6.5.1.**Do not abuse debconf Since debconf appeared in Debian, it has been widely abused and several criticisms received by the Debian distribution come from debconf abuse with the need of answering a wide bunch of questions before getting any little thing installed. Keep usage notes to what they belong: the NEWS.Debian, or README.Debian file. Only use notes for important notes which may directly affect the package usability. Remember that notes willalways block the install until confirmed or bother the user by email. Carefully choose the questions priorities in maintainer scripts. See debconf-devel(7) for details about priorities. Most questions should use medium and low priorities. 6.5.2.**General recommendations for authors and translators 6.5.2.1.**Write correct English Most Debian package maintainers are not native English speakers. So, writing properly phrased templates may not be easy for them. Please use (and abuse) [debian-l10n-english@ lists.debian.org] mailing list. Have your templates proofread. Badly written templates give a poor image of your package, of your work...or even of Debian itself. Avoid technical jargon as much as possible. If some terms sound common to you, they may be impossible to understand for others. If you cannot avoid them, try to explain them ( use the extended description). When doing so, try to balance between verbosity and simplicity. 6.5.2.2.**Be kind to translators Debconf templates may be translated. Debconf, along with its sister package po-debconf offers a simple framework for getting templates translated by translation teams or even individuals.
Breezy - Final Fantasy VIII Guitar Cover - Version 2
- Length: 2:46
- Rating: ( ratings)
- Views:
- Author: reiken87
Tags: Breezy Cover Fantasy Final Guitar Nobuo Squaresoft Uematsu VIII ギター 伸夫 植松
Longer because it's basically the same line repeated twice, different camera and using direct audio this time. I apologize for the text on the screen, that actually shouldn't be there but my camera is screwed up, so I'll probably buy a new one tomorrow. Enjoy, I mess up a bit, but it was fun.
Page: 1 of 16625