[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#715426: Bug # 715426: Interested in getting this done



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/25/2015 12:21 PM, Tianon Gravi wrote:
> Control: owner -1 tianon@debian.org
> 
> On Thu, 17 Sep 2015 16:26:35 -0400 "Roderick W. Smith" 
> <rod.smith@canonical.com> wrote:
>> I'm rEFInd's upstream maintainer and a Canonical employee, and
>> I'm interested in getting this packaged and the bug cleared.
> 
> Hey Roderick!  I'm interested in getting this package into the
> archive too, so I'd be glad to help out and be the Debian
> maintainer, especially with such an obviously engaged upstream. :)
> 
> I've created a repo in collab-maint (will show up at 
> https://anonscm.debian.org/cgit/collab-maint/refind.git
> eventually), and I'm currently working on getting your packaging
> ported over so I can evaluate what needs to change for Debian.
> It's probably worth taking a look at how "grub" and "lilo" handle
> the install stuff so we can mimic.

Thanks! FWIW, I made some changes to 0.10.0 to help get the packaging
ready, although I realize it's not quite there yet. I need to do
another pass through the files to get all the copyright details
properly documented and create some patches to get the post-install
script doing the right stuff (that is, not installing to the ESP
automatically).

I was actually looking at the GRUB 2 packaging the other day, but it's
VERY complex! I haven't looked at LILO, ELILO, SYSLINUX, or anything
else yet. One concern/question I have is how the OS knows which, if
any, boot loader should be installed. I'm not sure if this is an issue
with Debian, but Ubuntu has a habit of re-installing GRUB if it's
removed, which of course is annoying if you're using something else.
If there's some approved Debian way of recording what boot loader(s)
are in use, we should tie into that.

I was planning on doing more work on this packaging issue this
weekend, which is a long one in the US because of Thanksgiving.

- -- 
Rod Smith
Server and Cloud Certification Engineer
rod.smith@canonical.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJWVfHzAAoJEFgyRI+V0FjmTBwH/jJtL1r+5+Ye5Pg83o7P7amZ
/g95pwKuAv04IQX5I3reb2B/qxPWPRlY/fKeaDfOZchav/v04n6Fk1iuMc9iknaI
17XGhQx6s94wlKLEWQCoX0zlqJ3teUSaYdN+nzZd1Nph94HIqjtLEOQ9FK4qGeim
dLuVA/zKg/Jp6b0O8qpjXBaGrgOjvLLE1A07QEhUeO2SpWokva6QPUsTeZu/j8HG
LREq6jLoC2QEspEqGa+PgYv/yjP94d/zuI/bE7s1BGXvPSeOidbCcoxBvf6DLnp5
Tu/EhheE3DsZzmXB9cff1vLcMHuRSYc5iQ0oh/7rLms3HBjWbJFcTexZeEvXnrA=
=EIz6
-----END PGP SIGNATURE-----


Reply to: