On 27/11/15 15:35, Greg Beam wrote:
> Hi Barry, All,
>
> Just a couple things.
>
> I build allot of different applications, not just WSJTX. So to keep
> things straight I use INSTALLD and BUILDD both on Windows and Linux.
> Folks can use whatever name they like or nothing at all if that's a
> better fit for their purposes.
OK
>
> As for building the package along with the tarball, that's my choice, as
> I wont send anything to Launchpad without first having tested it
> locally, be it a stable branch or not. That's why it's in the script. It
> could easily be removed.

OK I understand, but I am generally building for the next distro release 
not the current stable that I am using now, so building in the local 
environment is not of much value. I test builds on my local build system 
which mimics that used by our distro build system, which pulls the base 
system and BuildRequires from the dev repo and builds in a chroot with 
only those files/libs etc. available.
I then install the built package in a running dev system to test.
>
> For my needs, there is a specific naming conversion the tarball must
> meet in order to build it with pbuilder ( local chroot ) as well as the
> build servers ( Launchpad ). Thus the reason for the long tarball name.
>
OK
> I build somewhere in the neighborhood of 18+ different packages from
> source on a routine basis (couple times per week at lease), times 4
> different distributions versions. I don't feel like typing all that out
> on the command line, so I use scripts for each one of them. YMMV.

Yes, I maintain about 88 packages and tend to make my own scripts where 
upstream tarballs are not available or releases lag way behind git or 
the sources are a bit unusual, like here.
Or simply just to aid my failing memory :)
>
> I m not sure about the install directory issue /usr or /usr/local, I've
> not ran into that problems before and don't see that problem Locally or
> on Launchpad. Maybe that's specific to your Distro's FSH.

Maybe, dunno - only seen it in the last few months.

Anyway - with everyone's excellent help here I have now pushed the 
package to the repos and it's working fine :)

Cheers,
Barry
G4MKT


>


------------------------------------------------------------------------------
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Reply via email to