Re: [blfs-dev] firefox-59.0
On 13/03/2018 15:51, Ken Moffat wrote: The latest firefox has now been released, but their process for offering the source has changed (not a surprise to me, they've been doing this for the 59 betas) - Speaking of FF, I just changed my default browser from seamonkey to FF. I have a question about configuration. I like to have the Menu Toolbar and Bookmarks Toolbar displayed. On SM, the order is: 1 Menu Toolbar 2 URL and Loading Controls Bar 3 Bookmarks 4 Tab Bar On FF it is 1 Menu Toolbar 4 Tab Bar 2 URL and Loading Controls Bar 3 Bookmarks Update: I started to ask how to do this, but google to the rescue. # Your default directory will be different cd ~/.mozilla/firefox/wraymktv.default/chrome cp userChrome-example.css userChrome.css vi userChrome.css At that point I added the text at https://www.userchrome.org/what-is-userchrome-css.html Third example. It may be overkill for Linux, but it works for me. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] firefox-59.0
On Tue, Mar 13, 2018 at 05:24:10PM +0100, Pierre Labastie wrote: > > We usually don't care much about the extracted directory name. I can give a > dozen of examples where the directory name does not match the package name, > and we do not say anything... > I suspect that many *new* readers of BLFS will assume that any package called foo-59.0 will untar to a directory called foo-59.0/ and will ask on the lists if it untars to something different. > So just provide the complete url, and make a note that if using wget, it may > be convenient to use the -O option to get a readable file name (but > personally, I never do that). And don't write about the extracted directory... > > > > > In either case, the book will need to note that the tarball creates > > a directory called mozilla-release-c61f5f5ead... (and I'm inclined > > to use dots rather than write out all 40 hex digits, except in the > > link). > > > > If my proposition is retained, that would not be a question anymore :) > > Pierre I'll think about rewording it (haven't started the timed 4-core build yet, so time to think about it). I'm not convinced about this approach, but maybe it is worth trying. I might keep some of what I've already started to prepare, but commented out until 60 is released - to see if it does cause mailing list comments. ĸen -- Truth, in front of her huge walk-in wardrobe, selected black leather boots with stiletto heels for such a barefaced truth. - Unseen Academicals -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] firefox-59.0
On 13/03/2018 15:51, Ken Moffat wrote: > The latest firefox has now been released, but their process for > offering the source has changed (not a surprise to me, they've been > doing this for the 59 betas) - > > The SOURCE file at > https://ftp.mozilla.org/pub/firefox/releases/59.0/SOURCE > is just some text telling you where to get the source. For the > .tar.bz2 that is > https://hg.mozilla.org/releases/mozilla-release/archive/c61f5f5ead48c78a80c80db5c489bdc7cfaf8175.tar.bz2 > > And if I use wget the default filename is c61f5f5ead... .tar.bz2 but > the directory within it is mozilla-release-c61f5f5ead.../ > > Fine if you have a wide screen in which to read the book ;) > > I suggest that we recommend using wget so that we can change the > filename, but I'm ambivalent about whether we should make the name > firefox-59.0.tar.bz2 or mozilla-release-c61f5f5ead... ? We usually don't care much about the extracted directory name. I can give a dozen of examples where the directory name does not match the package name, and we do not say anything... So just provide the complete url, and make a note that if using wget, it may be convenient to use the -O option to get a readable file name (but personally, I never do that). And don't write about the extracted directory... > > In either case, the book will need to note that the tarball creates > a directory called mozilla-release-c61f5f5ead... (and I'm inclined > to use dots rather than write out all 40 hex digits, except in the > link). > If my proposition is retained, that would not be a question anymore :) Pierre -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] firefox-59.0
On Tue, Mar 13, 2018 at 11:00:02AM -0500, Bruce Dubbs wrote: > > What does 'Help->About Firefox' say? > > -- Bruce > 59.0 (64-bit) The betas I tried all claimed to be 59.0 - the 58 betas all said they were -bNN ĸen -- Truth, in front of her huge walk-in wardrobe, selected black leather boots with stiletto heels for such a barefaced truth. - Unseen Academicals -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] firefox-59.0
On Tue, Mar 13, 2018 at 02:51:16PM +, Ken Moffat wrote: > > And if I use wget the default filename is c61f5f5ead... .tar.bz2 but > the directory within it is mozilla-release-c61f5f5ead.../ > > Fine if you have a wide screen in which to read the book ;) > > I suggest that we recommend using wget so that we can change the > filename, but I'm ambivalent about whether we should make the name > firefox-59.0.tar.bz2 or mozilla-release-c61f5f5ead... ? > > In either case, the book will need to note that the tarball creates > a directory called mozilla-release-c61f5f5ead... (and I'm inclined > to use dots rather than write out all 40 hex digits, except in the > link). > > Opinions ? > Looking at the firefox page, it already has a lot of Notes, so I'm expanding those. The download will point to the canonical site, using the full URL, but in one of the notes I will use a shortened URL with wget (the full one overflowed the boxes for the user input and for the note) - wget -c https://tinyurl.com/firefox-59-0-tar-bz2 \ -O mozilla-release-c61f5f5ead48c78a80c80db5c489bdc7cfaf8175.tar.bz2 I've checked the md5sums, both the c61f5f5e... and the mozilla-release-c61f5f5e... match (as expected), so I'll go with that. I've also put the 40-hex-digit hg version into an entity so that I can refer to it in the Notes. Looking at my working copy in links, the wget example fits inside 80 characters so it should be fully visible even in 80x25 terms. Now to measure it some more... ĸen -- Truth, in front of her huge walk-in wardrobe, selected black leather boots with stiletto heels for such a barefaced truth. - Unseen Academicals -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: [blfs-dev] firefox-59.0
On 03/13/2018 09:51 AM, Ken Moffat wrote: The latest firefox has now been released, but their process for offering the source has changed (not a surprise to me, they've been doing this for the 59 betas) - The SOURCE file at https://ftp.mozilla.org/pub/firefox/releases/59.0/SOURCE is just some text telling you where to get the source. For the .tar.bz2 that is https://hg.mozilla.org/releases/mozilla-release/archive/c61f5f5ead48c78a80c80db5c489bdc7cfaf8175.tar.bz2 And if I use wget the default filename is c61f5f5ead... .tar.bz2 but the directory within it is mozilla-release-c61f5f5ead.../ Fine if you have a wide screen in which to read the book ;) I suggest that we recommend using wget so that we can change the filename, but I'm ambivalent about whether we should make the name firefox-59.0.tar.bz2 or mozilla-release-c61f5f5ead... ? In either case, the book will need to note that the tarball creates a directory called mozilla-release-c61f5f5ead... (and I'm inclined to use dots rather than write out all 40 hex digits, except in the link). Opinions ? What does 'Help->About Firefox' say? -- Bruce -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
[blfs-dev] firefox-59.0
The latest firefox has now been released, but their process for offering the source has changed (not a surprise to me, they've been doing this for the 59 betas) - The SOURCE file at https://ftp.mozilla.org/pub/firefox/releases/59.0/SOURCE is just some text telling you where to get the source. For the .tar.bz2 that is https://hg.mozilla.org/releases/mozilla-release/archive/c61f5f5ead48c78a80c80db5c489bdc7cfaf8175.tar.bz2 And if I use wget the default filename is c61f5f5ead... .tar.bz2 but the directory within it is mozilla-release-c61f5f5ead.../ Fine if you have a wide screen in which to read the book ;) I suggest that we recommend using wget so that we can change the filename, but I'm ambivalent about whether we should make the name firefox-59.0.tar.bz2 or mozilla-release-c61f5f5ead... ? In either case, the book will need to note that the tarball creates a directory called mozilla-release-c61f5f5ead... (and I'm inclined to use dots rather than write out all 40 hex digits, except in the link). Opinions ? ĸen -- Truth, in front of her huge walk-in wardrobe, selected black leather boots with stiletto heels for such a barefaced truth. - Unseen Academicals -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
