[Scons-users] How to make Install depend on a command line target?

[Brian Raven]

> -----Original Message-----

> From: scons-users-bounces at scons.org [mailto:scons-users-

> bounces at scons.org] On Behalf Of William Deegan

> Sent: 25 June 2012 20:18

> To: SCons users mailing list

> Subject: Re: [Scons-users] How to make Install depend on a command line

> target?

>

> Brian,

>

> On Jun 25, 2012, at 3:52 AM, Brian Raven wrote:

>

> >> -----Original Message-----

> >> From: scons-users-bounces at scons.org [mailto:scons-users-

> >> bounces at scons.org] On Behalf Of William Deegan

> >> Sent: 23 June 2012 21:23

> >> To: SCons users mailing list

> >> Subject: Re: [Scons-users] How to make Install depend on a command

> >> line target?

> >>

> >> Brian,

> >>

> >> On Jun 15, 2012, at 7:21 AM, Brian Raven wrote:

> >>

> >> snip...

> >>>

> >>>>

> >>>>> [N.B. Using a pretty old version, v0.98.1.r2881. Not much choice

> >>>>> in the matter.]

> >>>>

> >>>> Wow, that's pretty ancient.  Could you just install a new version

> >>>> locally in your home dir or something?  Anyway, probably not

> >>>> related to this issue.  I just feel sorry for you. :-)

> >>>

> >>> I can do that, but many of the others in the global development

> team

> >> do not have the necessary permissions. They are the ones to feel

> >> sorry for.

> >>

> >> Can you expand upon this statement a bit?

> >> We're trying to better understand restrictive environments users may

> >> be using SCons in, in order to make it easier for them to use.

> >>

> >> Could your users not use the scons-local install?

> >

> > I'll try.

> >

> > The projects that I am working on involve development by teams spread

> around the globe. The policies for each team seem to be location

> dependant. For example I have full admin privileges for the Linux boxes

> that I use for development, so installing a later version of scons is

> not a problem for me. In other locations, developers do not have such

> freedom. They are not permitted to install anything on development

> boxes. Also, our build boxes have to use the version of scons that is

> part of the Linux distribution that is the build target.

> >

> > We have similar problems with other tools.

>

> You don't need to have admin privileges to install scons.. There's no

> limitation that it can only be installed in a system area.

>

> You could install in a common directory for your group or your home

> directory.

> And the scons-local is meant to be checked into your repo and used

> directly.

>

> Would you be barred from building a local version of python in your

> home directory or to a shared group directory or tools directory? (in

> your work environment?)

>

> I've never worked in an environment where i couldn't upgrade/build the

> tools I needed to build software, so I usually create a

> /COMPANY/PLATFORM/stow/TOOL-VERSION area to install in and then use

> stow (gnu stow) to manage the contents of /COMPANY/PLATFORM/bin

> occasionally, there'll be the need for  /COMPANY/PLATFORM/VERSION/...

>

> Then I check the sources and build scripts into whatever revision

> control system there is so the entire environment is reproducible.  The

> repo is usually then backed  up and put in source code escrow for many

> startups.


I know that it is possible to do that, but it is also local policy that prohibits such behaviour. At least that is what I am told bold by developers, and their managers, that work in other locations.

I think that it is understandable to a certain extent. The lowest common denominator approach does mean that, given the above limitation, the code base can be built everywhere, even if we can't use the features of the latest versions of our toolset.


--
Brian Raven




Please consider the environment before printing this e-mail.

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error, please advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy.

Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.