On Thu, 12 Nov 2020 at 22:35, Bruce Dubbs via lfs-dev
wrote:
>
> When LFS was originally developed, a single URL was deemed sufficient.
> When BLFS was started we wanted an ftp URL because LFS had an ftp
> client, but we also wanted to offer http access.
>
> Over the years, upstream has changed
On 11/12/20 12:37 AM, Kevin Buckley via lfs-dev wrote:
On Wed, 11 Nov 2020 at 23:57, Xi Ruoyao via lfs-dev
wrote:
Adding a link in package page will make it easier when some LFS package need to
be upgraded in a completed system.
--
Not sure that that's enough of a justification for having a
On Wed, 11 Nov 2020 at 23:53, Bruce Dubbs via lfs-dev
wrote:
>
> On 11/11/20 3:21 AM, Kevin Buckley via lfs-dev wrote:
> > I was recently trying to generate a downlaod listing of the packages I had
> > used
> > when building my Pkguser based 9.1 system, inclduing the BLFS components
> > that I'd
On 2020-11-11 09:53 -0600, Bruce Dubbs via lfs-dev wrote:
> On 11/11/20 3:21 AM, Kevin Buckley via lfs-dev wrote:
> > I was recently trying to generate a downlaod listing of the packages I had
> > used
> > when building my Pkguser based 9.1 system, inclduing the BLFS components
> > that I'd merged
On 11/11/20 3:21 AM, Kevin Buckley via lfs-dev wrote:
I was recently trying to generate a downlaod listing of the packages I had used
when building my Pkguser based 9.1 system, inclduing the BLFS components
that I'd merged into a single book.
FWIW, so as to see what I needed to download from
I was recently trying to generate a downlaod listing of the packages I had used
when building my Pkguser based 9.1 system, inclduing the BLFS components
that I'd merged into a single book.
FWIW, so as to see what I needed to download from BLFS 10.0
I noticed that in BLFS, where the package
