[Buildroot] Persistent tarball repository

[Buildroot] Persistent tarball repository

[MikeW]

I found to my annoyance that 'make distclean' clears out your downloaded .tar.gz
files in /dl, which could be a pain if you hadn't realised that (and was, since
there appears to be a problem with ftp.kernel.org so I got the file 'manually')

May I ask if there is a setting to allow these files to be cached somewhere that
'distclean' doesn't clear out ?
Might also be useful on a server in a team environment to ensure everyone
uses the same reference downloads without local duplication and time penalty.

Regards,
MikeW

[Buildroot] Persistent tarball repository

[Nathanael D. Noblet]

On Wed, 2006-11-01 at 14:23 +0000, MikeW wrote:
> I found to my annoyance that 'make distclean' clears out your downloaded .tar.gz
> files in /dl, which could be a pain if you hadn't realised that (and was, since
> there appears to be a problem with ftp.kernel.org so I got the file 'manually')
> 
> May I ask if there is a setting to allow these files to be cached somewhere that
> 'distclean' doesn't clear out ?
> Might also be useful on a server in a team environment to ensure everyone
> uses the same reference downloads without local duplication and time penalty.

make clean?
-- 
Nathanael D. Noblet <nathanael@gnat.ca>
Gnat Solutions, Inc

[Buildroot] Persistent tarball repository

[MikeW]

Nathanael D. Noblet <nathanael@...> writes:

> 
> On Wed, 2006-11-01 at 14:23 +0000, MikeW wrote:
> > I found to my annoyance that 'make distclean' clears out
 your downloaded .tar.gz
> > files in /dl, which could be a pain if you hadn't realised
 that (and was, since
> > there appears to be a problem with ftp.kernel.org
 so I got the file 'manually')
> > 
> > May I ask if there is a setting to allow these files
 to be cached somewhere that
> > 'distclean' doesn't clear out ?
> > Might also be useful on a server in a team environment
 to ensure everyone
> > uses the same reference downloads without local duplication
 and time penalty.
> 
> make clean?

Yes, but 'make clean' only removes object files, causing a straight rebuild from
source, 'distclean' is supposed to remove any make-generated/config files as
well - IIRC.

Which is not quite the same as deleting all your patiently downloaded
tarballs as well !

So I just wondered if there was a way to either allow distclean to spare
the package source files, or alternatively, if you could 'get' from a
local repository rather than having to download via FTP/HTTP, if your
required file existed.

Regards,
MikeW

[Buildroot] Persistent tarball repository

[Ashwin Bihari]

On 11/1/06, MikeW <mw_phil@yahoo.co.uk> wrote:
>
> Yes, but 'make clean' only removes object files, causing a straight
> rebuild from
> source, 'distclean' is supposed to remove any make-generated/config files
> as
> well - IIRC.
>
> Which is not quite the same as deleting all your patiently downloaded
> tarballs as well !
>
> So I just wondered if there was a way to either allow distclean to spare
> the package source files, or alternatively, if you could 'get' from a
> local repository rather than having to download via FTP/HTTP, if your
> required file existed.
>
> Regards,
> MikeW
>

Predominently, "make distclean" is used to return a package to it's
"distributed" state and in so that means removing any generated files and,
in Buildroots case, any downloaded files.

You can hack your Makefile to not remove the "dl" directory if you so wish,
but I would think that the system is behaving as expected.

You could also do the get from a local repository by modifying the
appropriate <package>.mk file in the "package" directory.

Regards

-- 
~ Ashwin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20061101/199d7333/attachment.htm 

[Buildroot] Persistent tarball repository

[MikeW]

Ashwin Bihari <abihari@...> writes:
 
> Predominently, "make distclean" is used to return a package to it's
"distributed" state and in so that means removing any generated files and, in
Buildroots case, any downloaded files.
> You can hack your Makefile to not remove the "dl" directory if you so wish,
but I would think that the system is behaving as expected.You could also do the
get from a local repository by modifying the appropriate <package>.mk file in
the "package" directory.
> Regards-- ~ Ashwin
>

Yes - I think my issue is that the downloads are held 'within' the buildroot
tree, hence the semantics of distclean as you describe them mean that they
must go.

If they were outside the buildroot tree, then I guess distclean ought not
to clear them out.

Wonder if that's the making of a patch - only 'distclean' delete
downloaded tarballs if they occur under the buildroot directory;
but currently there's no menuconfig option to say where downloads are kept ...
however at the moment I just want something that 'works out of the box'!

Thanks,
MikeW

[Buildroot] Persistent tarball repository

[Ashwin Bihari]

On 11/1/06, MikeW <mw_phil@yahoo.co.uk> wrote:
>
> Yes - I think my issue is that the downloads are held 'within' the
> buildroot
> tree, hence the semantics of distclean as you describe them mean that they
> must go.
>
> If they were outside the buildroot tree, then I guess distclean ought not
> to clear them out.
>
> Wonder if that's the making of a patch - only 'distclean' delete
> downloaded tarballs if they occur under the buildroot directory;
> but currently there's no menuconfig option to say where downloads are kept
> ...
> however at the moment I just want something that 'works out of the box'!
>
> Thanks,
> MikeW
>

Mike,

By all means provide a patch that allows you to change the location of the
DL directory and whether or not it should be deleted during a distclean. I
would definitely find it useful and if others agree, it might get committed.

Regards

-- 
~ Ashwin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://busybox.net/lists/buildroot/attachments/20061101/d24358a4/attachment.htm 

[Buildroot] Persistent tarball repository

[Marc Lindahl]

BR2_DL_DIR already there no patch needed... why do you need to move it 
around so much it needs to be in menuconfig?

also I disagree with patching distclean, then it will not behave the 
way all other distcleans everywhere behave.   Make a new option instead 
(though for the life of me I can't figure out what you'd need it for)

my $0.02,
Marc

On Nov 1, 2006, at 11:41 AM, Ashwin Bihari wrote:

> On 11/1/06, MikeW <mw_phil@yahoo.co.uk> wrote:
>>
>> tree, hence the semantics of distclean as you describe them mean that 
>> they
>> must go.
>>
>> If they were outside the buildroot tree, then I guess distclean ought 
>> not
>> to clear them out.
>>
>> Wonder if that's the making of a patch - only 'distclean' delete
>> downloaded tarballs if they occur under the buildroot directory;
>> but currently there's no menuconfig option to say where downloads are 
>> kept ...
>> however at the moment I just want something that 'works out of the 
>> box'!
>>
>> Thanks,
>> MikeW
>
> Mike,
>
> By all means provide a patch that allows you to change the location of 
> the DL directory and whether or not it should be deleted during a 
> distclean. I would definitely find it useful and if others agree, it 
> might get committed.
>
> Regards
>
> -- 
> ~ Ashwin_______________________________________________
> buildroot mailing list
> buildroot at uclibc.org
> http://busybox.net/mailman/listinfo/buildroot
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 1438 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20061101/38ba48dd/attachment.bin 

[Buildroot] Persistent tarball repository

[Bernhard Fischer]

On Wed, Nov 01, 2006 at 10:41:02AM -0600, Ashwin Bihari wrote:
>On 11/1/06, MikeW <mw_phil@yahoo.co.uk> wrote:
>>
>>Yes - I think my issue is that the downloads are held 'within' the
>>buildroot
>>tree, hence the semantics of distclean as you describe them mean that they
>>must go.
>>
>>If they were outside the buildroot tree, then I guess distclean ought not
>>to clear them out.
>>
>>Wonder if that's the making of a patch - only 'distclean' delete
>>downloaded tarballs if they occur under the buildroot directory;
>>but currently there's no menuconfig option to say where downloads are kept
>>...
>>however at the moment I just want something that 'works out of the box'!
>>
>>Thanks,
>>MikeW
>>
>
>Mike,
>
>By all means provide a patch that allows you to change the location of the
>DL directory and whether or not it should be deleted during a distclean. I
>would definitely find it useful and if others agree, it might get committed.

The DL_DIR will only be deleted if it's "dl" (i.e. the default). Change
it (via menuconfig; no need for an additional patch, it's already in
there).

You can "make dirclean" to clean everything but your .config and the
stuff in your custom DL_DIR.

HTH,

[Buildroot] Persistent tarball repository - already exists

[MikeW]

Ashwin Bihari <abihari@...> writes:

> 
> Mike,By all means provide a patch that allows you to change the location of
the DL directory and whether or not it should be deleted during a distclean. I
would definitely find it useful and if others agree, it might get committed.
> Regards-- ~ Ashwin
> 

Apologies to all, I take it all back - there /is/ a menuconfig option,
and if I specify /opt/dl, 'make distclean' does not clean it out !

Nice one, buildroot !

Now, back to the 'unrecognised emulation' problem ... grrr !

Regards,
MikeW

[Buildroot] Persistent tarball repository

[Peter Korsgaard]

>>>>> "Mike" == MikeW  <mw_phil@yahoo.co.uk> writes:

Hi,

Mike> May I ask if there is a setting to allow these files to be
Mike> cached somewhere that 'distclean' doesn't clear out ?  Might
Mike> also be useful on a server in a team environment to ensure
Mike> everyone uses the same reference downloads without local
Mike> duplication and time penalty.

We use a shared dl directory on a NFS server (setting
BR2_DL_DIR). Make distclean doesn't delete that.

-- 
Bye, Peter Korsgaard