similar to: Solaris packaging of rsync - script comes here

I've made some changes to buildpkg.sh to make it easier for package builders to add their local changes. I'd like people that use buildpkg.sh to test and comment on these changes before I commit them to CVS. None of the defaults have changed. Some of the patch is is just moving chunks of code to a different location to make some of the enhancements work. Some things you may find

Can someone else from the Solaris realm that uses our package system verify that this should be done? It looks right, but I want another opinion before commiting. - Ben > On Wed, 27 Feb 2002, Antonio Navarro wrote: > >> Hi Ben, >> >> I have made some modifications to the buildpkg.sh script that is >> distributed with openssh. >> >> I am sending it to

(Shame on me: wrong filename in last posting, now here are correct diffs) in contrib/solaris/ (openssh-SNAP-20011017.tar.gz) 1) buildpkg.sh makes wrong link for /etc/init.d/opensshd 2) /etc/init.d/opensshd has not-working killproc here my version tested on Solaris 2.4 and 8 (no pgrep with solaris 2.4, XARGS was undefined, simpler syntax) J?rg --- contrib/solaris/buildpkg.sh Fri Oct 12

The packaging/lsb/rsync.spec file is broken as shipped: It has a "Sept" month (rpmbuild here takes only 3-letter month names), and RH gzips the manpages, so the %files list can't find them. I also added doc/README-SGML and doc/rsync.sgml to the %doc files. Patch follows. Thanks for all the good work! --- rsync-2.5.6/packaging/lsb/rsync.spec.orig 2003-01-28 06:28:35.000000000 +0100

The following is a description of an rpm-based rsync build problem on my Redhat 7.1 system, and a patch that fixed the spec file. The problem occurred on several recent rsync releases, including 2.5.7: rpm -tb --define '_topdir /home/user/tmp/rpmbuild' rsync-2.5.7.tar.gz ALMOST works; it uses the spec file in lsb, not redhat/7.1. This spec file fails due to bad date format in one line,

Author: comay Repository: /hg/zfs-crypto/gate Revision: 995b6c053845811b23c196dc9e221620ed5ea04c Log message: 4907972 ON packages: more typos in pkginfo files 6403105 ON packages need update to satisfy new package audits Files: update: usr/src/pkgdefs/PHXext/pkginfo.tmpl update: usr/src/pkgdefs/SUNW1394/pkginfo.tmpl update: usr/src/pkgdefs/SUNW1394h/pkginfo.tmpl update:

SecureComputing's PAM library doesn't pass back the correct context to the pam_conversation function, i.e. it passes back NULL. So this patch works around this fact. likely you'll only want this hack if you expect to use pam_safeword.so in your authentication check, and only if you run sshd in privilege separation (separate process) mode so that the PAM conversation is single

Hi Martin, > thanks for the quick reply. I understand, that the generated code is different > between the two approaches. > But I would still expect IEEE rules to be respected in any case. I do not see > any reason why -fPIC -fomit-frame-pointer > and the like should have any impact on the results computed by the generated code. probably in the direct case you are using the x86

On Jun 5, 2012, at 3:20 AM, Martin Apel <martin.apel at SIMPACK.de> wrote: > I am trying to implement loop unrolling in a context, where lots of constant propagation has taken place. > Unrolling an outer loop might make an inner loop have constant bounds, therefore I want to process the loops > outside in, i.e. from parent loops to nested loops. > Unfortunately the standard loop

On Fri, Jul 15, 2011 at 12:21 AM, Martin Apel <martin.apel at simpack.de> wrote: > Hi all, > > I stumbled across a peculiarity regarding constant propagation that I don't understand. I'm not sure, if I oversee anything or if it's a missing feature. > > I have created the following simple test function in C: > > int times_zero(int a) > { >  return (a *

Hello... I have a big problem with asterisk. Every time i make a call asterisk does not bridge the zap channels. The zap channel from which i'm calling remains in state:ring and applicaton:dial and the zap channel with the external line configured remains in state:dialling an Application:AppDial. Zap/20-1 agentie s 1 Dialing AppDial (Outgoing Line) 09399 (None) Zap/9-1 int_omg 09399 5 Ring

Author: jongkis Repository: /hg/zfs-crypto/gate Revision: 8e73d99dab0952293f379aca3e88188d768b3a0b Log message: 6273535 SUNWgrub* packages have incorrect pkginfo(4) settings 6305469 READ_FAIL_STAGE2 in installgrub/message.h contains wrong message 6305481 installgrub miscounts stage2 size in sector by 1 if stage2 size is multiple of 512 6307439 make clobber in usr/src/grub and

Ok, I understand, now. I just leave multiple desktops in place and switch between them as I want. But perhaps you have reasons to do it as you do. That is one thing I really appreciate about Linux, the fact that there are many, many ways to accomplish almost everything and that what is right and works for me may not be what works best for you. Your scripting style is irrelevant so long as it

Le 26/02/2015 15:00, David Both a ?crit : > Perhaps I have not been following closely enough, but why go backwards? > Why not start with a "minimal" installation and then add only those > packages that are needed for your situation? Here's why. I'm currently experimenting with CentOS on my workstation, trying out different desktop environments like GNOME3, KDE, MATE,

Hi Duncan, thanks for the quick reply. I understand, that the generated code is different between the two approaches. But I would still expect IEEE rules to be respected in any case. I do not see any reason why -fPIC -fomit-frame-pointer and the like should have any impact on the results computed by the generated code. Are there any options I can set on the command line of llc to force the

On 07/24/2018 07:50 AM, Martin Maechler wrote: >>>>>> Benjamin Tyner >>>>>> on Sat, 21 Jul 2018 13:42:43 -0400 writes: > > Not sure whether it is the same issue as was raised here: > > https://stat.ethz.ch/pipermail/r-devel/2010-October/058729.html > > > but in any case perhaps the problem could partially be remedied on

On 24.07.2018 23:37, Benjamin Tyner wrote: > > > On 07/24/2018 07:50 AM, Martin Maechler wrote: >>>>>>> Benjamin Tyner >>>>>>> ???? on Sat, 21 Jul 2018 13:42:43 -0400 writes: >> ???? > Not sure whether it is the same issue as was raised here: >> ???? > https://stat.ethz.ch/pipermail/r-devel/2010-October/058729.html >>

Not sure whether it is the same issue as was raised here: https://stat.ethz.ch/pipermail/r-devel/2010-October/058729.html but in any case perhaps the problem could partially be remedied on line 245 of src/library/base/R/library.R by passing the lib.loc to .getRequiredPackages2() ...here is a patch (untested) Index: src/library/base/R/library.R

# cat iddmi.pp class iddmi { # define pkg variable $pkg = $hardwareisa ? { "sparc" => "Iddmi_SunOS_sparc.pkg", "i386" => "Iddmi_SunOS_i386.pkg", default => undef, } $ftpsystems = "ftp.example.net/download" # define path deafult for exec Exec { path =>

Hi guys, Which puppet operations should i try to avoid? I know that probably the most time consuming operations are file copies, but, is there something from the code point of view that I should try to avoid? I''ve seen for example, that on Solaris, puppet will execute pkginfo quite alot of times - sometimes with a package name, some other times without (pkginfo -l), thats extremely time